[
https://issues.apache.org/jira/browse/OAK-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389286#comment-14389286
]
Manfred Baedke commented on OAK-2705:
-------------------------------------
Yes. In the LDAP case, that would just be the DN, wouldn't it?
> DefaultSyncHandler should use the principalName as a fallback when no
> externalId is available
> ---------------------------------------------------------------------------------------------
>
> Key: OAK-2705
> URL: https://issues.apache.org/jira/browse/OAK-2705
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: oak-auth-external, upgrade
> Reporter: Manfred Baedke
>
> After a crx2oak repository migration, user nodes lack the property
> rep:externalId, which is needed for the DefaultSyncHandler to work properly.
> In the majority of cases (when there is only one ExternalIdentityProvider)
> using the principalName instead would work fine, so we should implement this
> as a fallback when rep:externalId is missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
