[jboss-jira] [JBoss JIRA] (ELY-698) Rework the constructor exclusion logic for authentication rules and configurations

[David Lloyd (JIRA)]

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

David Lloyd resolved ELY-698.
-----------------------------
    Fix Version/s: 1.1.0.Beta12
       Resolution: Done


> Rework the constructor exclusion logic for authentication rules and configurations
> ----------------------------------------------------------------------------------
>
>                 Key: ELY-698
>                 URL: https://issues.jboss.org/browse/ELY-698
>             Project: WildFly Elytron
>          Issue Type: Task
>          Components: Authentication Client
>            Reporter: David Lloyd
>            Assignee: David Lloyd
>            Priority: Minor
>             Fix For: 1.1.0.Beta12
>
>
> The current authentication rule and configuration classes are designed to ensure that mutually incompatible rules and configurations cannot coexist.  However the implementation is applied a bit erratically.  There may be problems with commutatively applying checks.  Some checks may be missing or extraneous.
> We need a new approach where the mutual exclusion set is somehow enforced centrally.  One option is to have literal sets, and each class that is a member of one or more sets must remove all other handlers that are also within the set(s).  A predicate could be used to make this efficient by only sweeping the list one time, in contrast to the current mechanism which sweeps the list once per exclusive type.
> Another option is to have a marker interface for each capability, and to remove all peers with the same capability.  A predicate can also be used in this case.



--
This message was sent by Atlassian JIRA
(v7.2.2#72004)