5:20 a.m.
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.CR1
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
12:30 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8025) Fix setting of custom SecurityManager class
[
https://jira.jboss.org/jira/browse/JBAS-8025?page=com.atlassian.jira.plug...
]
Anil Saldhana commented on JBAS-8025:
-------------------------------------
The static maps in JNDIBasedSecurityManagement need to be populated before the
SecurityDomainObjectFactory is instantiated by jndi.
So try reversing the JNDIBasedSecurityManagement bean definition and the
JNDIContextEstablishment bean definition in deploy/security/security-jboss-beans.xml
In the JNDIBasedSecurityManagement bean, set the authenticationMgrClass property.
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.CR1
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
1:03 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8025) Fix setting of custom SecurityManager class
[
https://jira.jboss.org/jira/browse/JBAS-8025?page=com.atlassian.jira.plug...
]
Anil Saldhana commented on JBAS-8025:
-------------------------------------
Changing the order of those two beans starts the AS6 instance perfectly and the test suite
has no issues.
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.CR1
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
11:14 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8025) Fix setting of custom SecurityManager class
[
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
4:18 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-8025) Fix setting of custom SecurityManager class
[
https://jira.jboss.org/browse/JBAS-8025?page=com.atlassian.jira.plugin.sy...
]
Anil Saldhana reassigned JBAS-8025:
-----------------------------------
Assignee: Marcus Moyses (was: Anil Saldhana)
Fix setting of custom SecurityManager class
-------------------------------------------
Key: JBAS-8025
URL: https://jira.jboss.org/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: Marcus Moyses
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:29 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-8025) Fix setting of custom SecurityManager class
[
https://jira.jboss.org/browse/JBAS-8025?page=com.atlassian.jira.plugin.sy...
]
Marcus Moyses resolved JBAS-8025.
---------------------------------
Resolution: Done
Fixed setting of custom SecurityManager and CallbackHandler classes now that
JNDIBasedSecurityManagement starts first.
Fix setting of custom SecurityManager class
-------------------------------------------
Key: JBAS-8025
URL: https://jira.jboss.org/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: Marcus Moyses
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5056
days inactive
5110
days old
5 comments
2 participants
participants (2)
-
Anil Saldhana (JIRA) -
Marcus Moyses (JIRA)