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 2015/03/30 17:49:53 UTC

[jira] [Assigned] (OAK-2705) DefaultSyncHandler should use the principalName as a fallback when no externalId is available

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

Manfred Baedke reassigned OAK-2705:
-----------------------------------

    Assignee:     (was: Manfred Baedke)

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