[jboss-jira] [JBoss JIRA] (ELY-1173) InvalidNameState not used for non-existing identities in ServerAuthenticationContext

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/ELY-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465672#comment-13465672 ] 

David Lloyd commented on ELY-1173:
----------------------------------

In this context "invalid name" means that the name did not pass validation.  A valid name which is nevertheless not found is not the same issue (as such a name may later be found, for example).  I don't think we need a persistent state for not-found names.

> InvalidNameState not used for non-existing identities in ServerAuthenticationContext
> ------------------------------------------------------------------------------------
>
>                 Key: ELY-1173
>                 URL: https://issues.jboss.org/browse/ELY-1173
>             Project: WildFly Elytron
>          Issue Type: Bug
>            Reporter: Jan Kalina
>            Assignee: Jan Kalina
>            Priority: Minor
>
> There was added new state *InvalidNameState* into *ServerAuthenticationContext* as part of ELY-1115, but it is currently used only when principal is rewritten to null - not when identity is not found in security realm.
> After adding this will be probably necessary to implement more State methods in *InvalidNameState* to have wildfly tests green.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)