[
https://issues.apache.org/jira/browse/OAK-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452501#comment-16452501
]
Manfred Baedke commented on OAK-7428:
-------------------------------------
[~anchela],
Yes, see
https://issues.apache.org/jira/browse/OAK-7428?focusedCommentId=16448087&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16448087.
I'd prefer to use just one flag indicating if the user id/group name should be
used, which have to be unique and immutable anyway. See attached
[^oak-7428.patch] - tests are running, commit will follow tomorrow.
Re config params: That's true, that one change doesn't belong here. Since we
actually have multiple config params that have never been documented (e.g.
connection pool related options), I'll create a new issue for all of them.
> LdapIdentityProvider doesn't support creating external ids from custom
> attributes
> ---------------------------------------------------------------------------------
>
> Key: OAK-7428
> URL: https://issues.apache.org/jira/browse/OAK-7428
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: auth-ldap
> Reporter: Manfred Baedke
> Assignee: Manfred Baedke
> Priority: Major
> Attachments: oak-7428.patch
>
>
> The LdapIdentityProvider always uses the value of an authorizables DN to
> create external ids. But DNs may change over time, while the external id of
> an authorizable have to be stable because the property rep:externalID is
> protected.
> Therefore we need to add the option to use the value of a configurable LDAP
> attribute to create external ids from it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
