[
http://jira.jboss.com/jira/browse/JBAS-3535?page=all ]
Anil Saldhana updated JBAS-3535:
--------------------------------
Description:
Scott mentioned that it is easier to use JNDI for obtaining the authorization manager
rather than relying on the JMX service wrapper (AuthorizationManagerService). So once the
authorization manager is bound in JNDI, should be obtainable just like the securitymgr
(aka AuthenticationManager plus RealmMapping)
Binding via JNDI is easier for the MC integration in this case.
was:Scott mentioned that it is easier to use JNDI for obtaining the authorization
manager rather than relying on the JMX service wrapper (AuthorizationManagerService). So
once the authorization manager is bound in JNDI, should be obtainable just like the
securitymgr (aka AuthenticationManager plus RealmMapping)
Make AuthorizationManager injectable via JNDI
---------------------------------------------
Key: JBAS-3535
URL:
http://jira.jboss.com/jira/browse/JBAS-3535
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: JBossAS-5.0.0.Beta
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-5.0.0.Beta
Scott mentioned that it is easier to use JNDI for obtaining the authorization manager
rather than relying on the JMX service wrapper (AuthorizationManagerService). So once the
authorization manager is bound in JNDI, should be obtainable just like the securitymgr
(aka AuthenticationManager plus RealmMapping)
Binding via JNDI is easier for the MC integration in this case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira