Updating User Information from EntraID in Collibra via SSO
Summary: Hans Kappert raised an issue about not being able to propagate updates of user first names and last names from EntraID to Collibra via Single Sign-On (SSO). This has been problematic as direct user modifications in Collibra are not possible due to SSO-created accounts. Nuriia Rose mentioned they also update user information from EntraID but haven't encountered this problem. Heather Fara shared experiences with similar integration challenges and provided practical advice, such as maintaining alert systems for OAuth token renewals and backup strategies, cautioning about the impact of user deletions on relationships and data integrity.
We've implemented Single Sign-On (SSO) with EntraID for user authentication in Collibra. However, we've encountered a challenge where updates to user information, specifically changes in firstname and lastname in EntraID, are not being propagated to Collibra. Direct modifications in Collibra aren't feasible as the users are created via SSO. How have others approached updating user data in Collibra when changes occur in the identity provider like EntraID? Have you found any solutions or workarounds to ensure that Collibra reflects the latest user information without manual intervention? Please share your insights or experiences with similar integration challenges.
Heather Fara
·4 months ago · EditedI have not seen that behavior but could test it next week if you like. I did have an issue with scim not reading a group name change, so we created another group and manually deleted the first group in Collibra.
Collibra documentation is terrible right now and l don’t see a place to comment on it, so adding a few missing nuggets people miss here:
You must code out the colons in Entra when setting up the handshake.
Set up an alert outside Collibra to renew each OAuth token every 11mos because that will stop sync
Collibra assigns a UIID for every user, so if you delete them you will loose all relationships for that user - loss of stewardship info, groups, their drafts, preferences among other things. If you have to back everything up and get ready to potentially manually restore (often fastest).
One user can have multiple accounts with same address for reason above (good thing), so it can create issues down line if you are syncing multiple Entra instances
Nuriia Rose
·4 months agoWe also update user information from Entra ID via SSO. But we did not yet face the challenge of changes in firstname and lastname.