[jboss-jira] [JBoss JIRA] Updated: (JBAS-4410) JaasSecurityDomain settings need to be sent to SecurityConfiguration

[Dimitris Andreadis (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dimitris Andreadis updated JBAS-4410:
-------------------------------------

    Fix Version/s:     (was: JBossAS-5.0.0.CR2)


Please re-schedule again when you know you have time to work on that.

> JaasSecurityDomain settings need to be sent to SecurityConfiguration
> --------------------------------------------------------------------
>
>                 Key: JBAS-4410
>                 URL: https://jira.jboss.org/jira/browse/JBAS-4410
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: Anil Saldhana
>            Assignee: Anil Saldhana
>
> SECURITY-26 has a need for the MBean services and other security related integration aspects for the JBAS to get back into the AS workspace. I see an issue with the Ldapxxx login modules having a reliance on the DecodeAction privileged action, that internally used to call the JaasSecurityDomain mbean service to decode a b64 string.  Now since the JaasSecurityDomain mbean service was the central source of the various jsse/crypto settings, we need to get away from this model and use the static SecurityConfiguration as the sink for the security settings.  This static SecurityConfiguration can be populated from JaasSecurityDomain Mbean service, the security deployer or wherever.
> There certainly has to be a better way than the static SecuriytConfiguration. For now, it is sufficient.

-- 
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