[OAK-5210] Ability to resolve principal name from ExternalIdentityRef without IDP roundtrip

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.0, 1.6.1, 1.8.0
• Component/s: auth-external
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 01/Dec/16 16:57
• Updated: 24/May/17 13:05
• Resolved: 08/Feb/17 16:11

Description

Currently the only way to reliably determine the principal name for a given external identity is by calling ExternalIdentity.getPrincipalName(). This also means that there is currently no way to resolve the principal name from a given ExternalIdentityRef, without calling ExternalIdentityProvider.getIdentity(ExternalIdentityRef).

In the default sync mode a given identity-ref will always be resolved to the associated identity once a given identity is up for (re)sync and thus the identity resolution is part of the synchronization. On the other hand the partial sync as provided by the DynamicSyncContext doesn't require the resolution of group identities but only needs to be able to obtain the principal name, which is needed to proper populate the subject upon repository login (and for permission setup for those group principals). In this setup it would be preferrable if the principal name could be resolved from the ExternalIdentityRef without the intermediate identity resolution.

This aim of this issue is to discuss the different options on how to achieve this improvement in a generic way that doesn't make any assumptions regarding the relationship between ExternalIdentity.getId, ExternalIdentity.getPrincipalName and ExternalIdentityRef.getId.

See also OAK-4930 and OAK-5200 for additional information.

Issue Links

• is duplicated by: OAK-5209 Save roundtrips to external identity servers
• relates to: OAK-5200 OAK-4930 introduced critical bug confusing id and principal name
• supercedes: OAK-4930 External Principal Management: DynamicSyncContext makes redundant calls to IdentityProvider.getIdentity()