[jboss-jira] [JBoss JIRA] Reopened: (SECURITY-262) JASPIAuthenticationInfo must override merge in order to merge the login-module stacks
Anil Saldhana (JIRA)
jira-events at lists.jboss.org
Mon Oct 13 10:01:21 EDT 2008
[ https://jira.jboss.org/jira/browse/SECURITY-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anil Saldhana reopened SECURITY-262:
------------------------------------
> JASPIAuthenticationInfo must override merge in order to merge the login-module stacks
> -------------------------------------------------------------------------------------
>
> Key: SECURITY-262
> URL: https://jira.jboss.org/jira/browse/SECURITY-262
> Project: JBoss Security and Identity Management
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: AS-Integration
> Affects Versions: 2.0.2.CR6
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
> Fix For: 2.0.2.CR7
>
>
> JASPIAuthenticationInfo currently inherits the merge method from BaseSecurityInfo. As a result, the login-module-stacks are lost during the merge process because the inherited merge implementation creates a new instance of JASPIAuthenticationInfo that contains only the merged auth-modules. To avoid this we must override the merge method in JASPIAuthenticationInfo to make sure the login-module-stacks are also merged in the final object.
> Also, the ApplicationPolicy should not allow the merge of authentication and authentication-jaspi methods, as only one of the configurations is allowed per policy. This means that a verification is needed in order to make sure that a policy doesn't extend a parent policy that specifies a different type of authentication.
--
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
More information about the jboss-jira
mailing list