You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Manfred Baedke (JIRA)" <ji...@apache.org> on 2016/11/08 14:34:59 UTC

[jira] [Commented] (OAK-4820) oak-auth-external can't handle full-width logins

    [ https://issues.apache.org/jira/browse/OAK-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647713#comment-15647713 ] 

Manfred Baedke commented on OAK-4820:
-------------------------------------

Added tests to trunk: r1768701.

> oak-auth-external can't handle full-width logins
> ------------------------------------------------
>
>                 Key: OAK-4820
>                 URL: https://issues.apache.org/jira/browse/OAK-4820
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: auth-external, core, security
>    Affects Versions: 1.0.33, 1.4.7, 1.2.19
>            Reporter: Manfred Baedke
>            Assignee: Manfred Baedke
>            Priority: Minor
>             Fix For: 1.6
>
>
> oak-auth-external should optionally be able to conform to https://tools.ietf.org/html/rfc7613, since the external authentication server might do so (seen in the wild with LDAP auth against Active Directory).
> For Oak this means that the AuthorizableBaseProvider should be able to generate identical content IDs for strings that are equivalent according to the UsernameCaseMapped Profile defined in https://tools.ietf.org/html/rfc7613#section-3.2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)