[jopr-issues] [JBoss JIRA] Resolved: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials

[Ian Springer (JIRA)]

     [ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Springer resolved JOPR-9.
-----------------------------

    Resolution: Done


Fixed using Greg's suggested fix - MC4J r594, RHQ r1889. 

Note, after svn up'ing to RHQ r1889, people should do a clean build of the jmx plugin to make sure the EMS 1.2.5 jar gets purged from the plugin's lib dir.


> Cannot handle multiple JBossAS connections with different credentials
> ---------------------------------------------------------------------
>
>                 Key: JOPR-9
>                 URL: https://jira.jboss.org/jira/browse/JOPR-9
>             Project: Jopr
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Greg Hinkle
>            Assignee: Ian Springer
>             Fix For: 2.2
>
>
> Opened from RHQ-1030...
> Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads.
> After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs.
>         SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-"));
>         SecurityAssociation.setCredential("-credentials-");

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira