[
http://jira.jboss.com/jira/browse/JBAS-5312?page=all ]
Stefan Guilhen closed JBAS-5312.
--------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-5.0.0.CR2)
Resolution: Done
The whole metadata work has been moved to a new module under the security project and
tests have been added. The security assembly project includes the factory and the beans in
the jbosssx.jar file that is used by the AS.
It is also possible now to get references to the security managers through the application
policy configuration, as in the example bellow:
<deployment xmlns="urn:jboss:bean-deployer:2.0">
<application-policy xmlns="urn:jboss:security-beans:1.0"
name="somepolicy">
<authentication>
<login-module
code="org.jboss.security.auth.spi.UsersRolesLoginModule"
flag="required">
<module-option
name="usersProperties">testusers.properties</module-option>
<module-option
name="rolesProperties">testroles.properties</module-option>
</login-module>
</application-policy>
...
<bean name="someBean" class="org.somepackage.SomeClass">
<property name="authManager"><inject bean="somepolicy"
property="authenticationManager"/></property>
</bean>
...
</deployment>
In the example, the bean "someBean" retrieves an AuthenticationManager reference
through the application-policy bean that is generated by the metadata factory. The manager
retrieved is responsible for providing authentication according to the specified policy.
Other managers available include the authorizationManager, roleMappingManager,
auditManager and identityTrustManager.
Make DynamicLoginConfig a bean
------------------------------
Key: JBAS-5312
URL:
http://jira.jboss.com/jira/browse/JBAS-5312
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Anil Saldhana
Assigned To: Stefan Guilhen
Fix For: JBossAS-5.0.0.CR1
Just the way XMLLoginConfig was made into a bean with an additional @JMX annotation,
Dynamic LoginConfig needs to be made into a bean. Any internal attributes that use
ObjectNames (if any) need to be injectable.
An usage of DynamicLoginConfig is in deploy/security-policies-service.xml
--
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