The legacy mbean services like jaassecuritymanagerservice etc need to be retained in the security module of the jbas build for porting customers. This is according to Scott.
===
The security mbeans really should be back in the jbossas/security as integration code so that the security project is a mc/pojo based set of security aspects.
I'm talking about the legacy mbeans which we should keep for porting.
===
- is blocked by
-
JBAS-4410 JaasSecurityDomain settings need to be sent to SecurityConfiguration
- Closed