Skip to content

exposeAccessContext should also be available for JndiRmiClientInterceptor [SPR-9428] #14063

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

Closed
spring-projects-issues opened this issue May 21, 2012 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: backported An issue that has been backported to maintenance branches type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Sylvain LAURENT opened SPR-9428 and commented

I expose some spring beans in Weblogic using the JndiRmiServiceExporter .
To use such beans, on the client side I use JndiRmiProxyFactoryBean.

Everything works well, except that the RMI calls are done anonymously eventhough the credentials are specified in the JNDI environment of the jndiTemplate.
After investigation, the problem seems to be that the JNDI context is not kept open during remote method calls, it is created when the stub is created but immediately closed.

For EJB remote calls there is the property exposeAccessContext on AbstractSlsbInvokerInterceptor which exists for this Weblogic case.
The same property should be available on the class JndiRmiClientInterceptor to provide the same feature, that is creating an InitialContext before the remote call and closing it after. Without such a feature, it is impossible to use security with Spring remoting and RMI/weblogic


Affects: 3.0.6

Referenced from: commits cca255b, c374389

Backported to: 3.1.4

@spring-projects-issues spring-projects-issues added status: backported An issue that has been backported to maintenance branches type: enhancement A general enhancement in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.2.1 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: backported An issue that has been backported to maintenance branches type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants