[jboss-jira] [JBoss JIRA] Resolved: (JBAS-5996) Drop TomcatDeployer.securityManagerService

[Scott M Stark (JIRA)]

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

Scott M Stark resolved JBAS-5996.
---------------------------------

    Resolution: Done


We are still using the JaasSecurityManager in the war SecurityAssociationValve to fush the auth cache on session validation, so I just moved the injection of the jboss.security:service=JaasSecurityManager to the deploy/jbossweb.sar from the deployers/jbossweb.deployer.


> Drop TomcatDeployer.securityManagerService
> ------------------------------------------
>
>                 Key: JBAS-5996
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5996
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-5.0.0.CR2
>            Reporter: Scott M Stark
>            Assignee: Scott M Stark
>             Fix For: JBossAS-5.0.0.GA
>
>
> The TomcatDeployer as a securityManagerService that is set using injection of the jboss.security:service=JaasSecurityManager mbean. There is just propagated down to the deployment. It should be a dependency inject setup in the deployment based on the name. We seem to already have a duplicate injection setting coming from the securityManagementName which is already injected in the deployment. The securityManagerService should just be dropped from the deployer.

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