-
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 #17368
Comments
alzimmermsft
added
Client
This issue points to a problem in the data-plane of the library.
common
common module used by all azure SDKs (e.g. client, Mgmt)
Epic
labels
Nov 9, 2020
This was referenced Nov 9, 2020
rjernst
added a commit
to fcofdez/elasticsearch
that referenced
this issue
Dec 2, 2020
The azure sdk internally dynamically constructs its client classes. However, one of these, for the blob storage is private. This has been fixed upstream, but until that is released, the client is unuseable without the newProxyInPackage permission. Rather than grant that permission, this commit makes the class in question public by patching the azure class file when building the azure repository plugin. relates Azure/azure-sdk-for-java#17368
It's important to mention that to make interfaces public you need to add |
6 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When an application uses
SecurityManager
there us the possibility thatRestProxy
would throw an exception when instantiating a client. This is thrown whenReflectPermission
isn't given to the implementation interface and the interface isn't publicly scoped. Given that, by default, the implementation interface is generated in theimplementation
package this could be made public preventing the chance for this issue being thrown. The latest versions of AutoRest has been updated to generate the implementation interface as public preventing this issue from happening by configuring the following:Perform the following to test and verify whether your clients are affected by the issue, if they are you'll need to regenerate with the newest code generator.
policy
file with this configuration:HttpClient
, all that needs to be done is the client being built.SecurityManager
turned on. Pass-Djava.security.manager
and-Djava.security.policy=<location of the policy file you created>
.The text was updated successfully, but these errors were encountered: