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

2016-11-08 Thread Manfred Baedke (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-4820:

Fix Version/s: 1.5.11

> 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, 1.5.11
>
>
> 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)


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

2016-11-08 Thread Manfred Baedke (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-4820:

Description: 
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.

  was:
oak-auth-external should be 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.


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


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

2016-09-19 Thread Manfred Baedke (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-4820:

Component/s: security
 core

> 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
>
> oak-auth-external should be 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)


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

2016-09-19 Thread Manfred Baedke (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-4820:

Affects Version/s: (was: 1.4.7)

> 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
>Affects Versions: 1.0.33, 1.4.7, 1.2.19
>Reporter: Manfred Baedke
>Assignee: Manfred Baedke
>Priority: Minor
>
> oak-auth-external should be 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)


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

2016-09-19 Thread Manfred Baedke (JIRA)

 [ 
https://issues.apache.org/jira/browse/OAK-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Manfred Baedke updated OAK-4820:

Affects Version/s: 1.4.7

> 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
>Affects Versions: 1.0.33, 1.4.7, 1.2.19
>Reporter: Manfred Baedke
>Assignee: Manfred Baedke
>Priority: Minor
>
> oak-auth-external should be 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)