[
https://jira.jboss.org/jira/browse/JBAS-8025?page=com.atlassian.jira.plug...
]
Marcus Moyses commented on JBAS-8025:
-------------------------------------
Changing the order doesn't solve the issue. The static map only gets an entry when
some component looks up a security domain in the JNDI. When that happens,
SecurityDomainObjectFactory populates the static map using the default
AuthenticationManager (because it creates a default JNDIBasedSecurityManagement instance
and uses it to invoke createSecurityDomainContext(securityDomain).
Fix setting of custom SecurityManager class
-------------------------------------------
Key: JBAS-8025
URL:
https://jira.jboss.org/jira/browse/JBAS-8025
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: 6.0.0.M3
Reporter: Marcus Moyses
Assignee: Anil Saldhana
Fix For: 6.0.0.M4
Setting the attribute SecurityManagerClassName in conf/jboss-service.xml to a custom name
has no effect. JBoss is always using the default class.
Also setting the authenticationMgrClass property of JNDIBasedSecurityManagement bean has
no effect either.
--
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