-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regenerate Implementation Layer with Interface Scoping Changes #12829
Comments
Thank you for submitting this issue @jspenc4, I'll take a look into reproducing it and finding possible solutions when dealing with strict |
@YijunXieMS, the AutoRest V4 code generator was updated by @srnagar in the mentioned PR to generate the Swagger interface as public so it doesn't run into this issue anymore. This is a longer term fix that will get resolved as clients regenerate their Swaggers. |
Renamed, see #17368 for instructions on resolving this issue. |
@rickle-msft @gapra-msft this should be resolved by updating the code generator used. |
Is there any approximate time when this will be tackled? We would like to avoid giving that permission on our security policy. |
@fcofdez I think the earliest would be in our January release, though I can't say for certain whether it will make it in there. I'll update here as I get more information |
[Hub Generated] Review request for Microsoft.Cache to add version stable/2021-03-01 (#12829) * Adds base for updating Microsoft.Cache from version preview/2020-10-01-preview to version 2021-03-01 * Updates readme * Updates API version in new specs and examples * Add support for persistence and fix other typos * Fix SDK Warning: R2063 OperationIdNounConflictingModelNames * Fix spellcheck error * Fix acronym capitalization in descriptions * Replace local parameters with common-types parameters * Use naming convention consistent with Azure documentation * Update word choice, remove deprecated x-ms-code-generation-setting, and fix operationId * Add x-ms-secret extension and make TLS version a string enum * Suppress errors about secrets being sent in responses
[Hub Generated] Review request for Microsoft.Cache to add version stable/2021-03-01 (#12829) * Adds base for updating Microsoft.Cache from version preview/2020-10-01-preview to version 2021-03-01 * Updates readme * Updates API version in new specs and examples * Add support for persistence and fix other typos * Fix SDK Warning: R2063 OperationIdNounConflictingModelNames * Fix spellcheck error * Fix acronym capitalization in descriptions * Replace local parameters with common-types parameters * Use naming convention consistent with Azure documentation * Update word choice, remove deprecated x-ms-code-generation-setting, and fix operationId * Add x-ms-secret extension and make TLS version a string enum * Suppress errors about secrets being sent in responses
This will be resolved with this PR #18907 |
Hi @fcofdez We recently shipped a beta release of the storage libraries with this fix. Could you please try that out and let me know how it goes? I believe the version is azure-storage-blob 12.11.0-beta.2 + |
Closing as the issue was resolved with the latest version of GAd storage libraries |
Query/Question
how can i solve
java.security.AccessControlException: access denied ("java.lang.reflect.ReflectPermission" "newProxyInPackage.com.azure.storage.blob.implementation")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
at java.security.AccessController.checkPermission(AccessController.java:884)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.lang.reflect.Proxy.checkNewProxyPermission(Proxy.java:770)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:726)
at com.azure.core.http.rest.RestProxy.create(RestProxy.java:683)
at com.azure.core.http.rest.RestProxy.create(RestProxy.java:665)
at com.azure.storage.blob.implementation.ServicesImpl.(ServicesImpl.java:58)
at com.azure.storage.blob.implementation.AzureBlobStorageImpl.(AzureBlobStorageImpl.java:216)
at com.azure.storage.blob.implementation.AzureBlobStorageBuilder.build(AzureBlobStorageBuilder.java:93)
at com.azure.storage.blob.BlobServiceAsyncClient.(BlobServiceAsyncClient.java:110)
at com.azure.storage.blob.BlobServiceClientBuilder.buildAsyncClient(BlobServiceClientBuilder.java:109)
at com.azure.storage.blob.BlobServiceClientBuilder.buildClient(BlobServiceClientBuilder.java:82)
Why is this not a Bug or a feature Request?
A clear explanation of why is this not a bug or a feature request?
it does seem like a bug to me. however, hoping i misunderstand.
my attempts to edit the java.policy file to allow Reflect Permission are failing.
and in any case, my security team will not let me allow it.
Setup (please complete the following information if applicable):
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: