[
https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin....
]
Ian Springer commented on JOPR-9:
---------------------------------
REPRO STEPS
=============
Setup 5 or more JBossAS and/or JBossEAP instances *all on the same machine* (you'll
want to bind each instance to a different IP - e.g., 127.0.0.1, 127.0.0.2, etc.). For each
instance:
1) Make sure authentication is enabled for the JMX invoker service (uncomment the block in
deploy/jmx-invoker-service.xml).
2) Set it up to use a unique username and password in
conf/props/jmx-console-users.properties, e.g.:
instance1: admin1:admin1
instance2: admin2:admin2
instance3: admin3:admin1
instance4: admin4:admin4
instance5: admin4:admin5
Note, for two of the instances, use the same username, but different passwords (like
instance4 and instance5 above).
3) Start up the instance and let JON discover it.
4) Import the discovered resource.
5) Edit its conn props and set the username and password to the correct values for the
instance.
6) Verify that the instance turns green.
Once all instances are green, let the AS instances and the JON Server and Agent run for a
few hours. Check periodically and make sure all instances are still green and that there
are no EMS connection/authentication errors in the Agent log.
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