User Profiles for Confluence (Microsoft Attributes Sync)

Problem Synchronizing Multiple User Directories UPC

🤔 Problem

  • While synchronizing user data from configured user directories, the directories are currently processed in the same order as defined.

    • I.e., if there are 3 directories, A, B, and C, data for users in directory A will be processed before data for directory B, and data for directory C will be processed last.

  • This might cause problems if users appear in more than one directory and have different data stored for them in each directory.

    • If, e.g., user "Bob" exists in directories A and C, and only has data stored in directory A, then the data from A would be overridden with the data from C. Since no data is stored in C, the profile elements will remain empty for Bob.

  • The only way to prevent this is to change the order of the user directories, which might cause other problems (e.g., directory C wins over A for authentication, which is standard Confluence behavior).

🧐 Cause

Occurs if a specific user is synchronized from two or more directories into Confluence.

The user's display name and email address will be taken from the first directory where the user is found (in the directory order within Confluence administration).

All additional user profile elements for this user (configured via the user profile plugin administration) will be taken from the last directory where the user is found.

Atlassian does not recommend synchronizing the same user across different directories.

🌱 Solution / Workaround

Allowing us to reverse the order in which directories are processed would provide a simple solution to this specific problem.

However, this would not help if the relevant information is stored in directory B and the user exists in all 3 user directories.

We cannot simply reverse the processing order by default, because some customers rely on the current implementation. So this feature has to be opt-in.