Basically, you can use User Profiles for Confluence with Crowd, but there is a catch: The synchronization feature of User Profiles for Confluence only supports directly connected LDAP-based directories, like Active Directory.
So, what will work?
-
You can add new profile elements.
-
Fields can be filled by your users.
-
Search for profile information within Confluence.
-
Use User Profiles for Confluence macros.
And what won't?
-
Synchronizing data from any directory that is connected via Crowd or delegated directories.
Examples:
-
Synchronizing constellation:
-
Confluence --> LDAP/Active Directory
-
-
Non-synchronizing constellations:
-
Confluence --> JIRA --> Active Directory/LDAP
-
Confluence --> JIRA --> Crowd --> Active Directory/LDAP
-
Confluence --> Crowd --> Active Directory/LDAP
-
Synchronizing User Profiles for Confluence with Crowd is not currently supported, but a workaround is available.
The workaround is to add the user directory containing the desired user information as a second user directory to your Confluence. This will then be connected to the Crowd. (For more info, see the Atlassian documentation.)
There are several constraints for this scenario:
-
The order of the directories in the configuration is important. The Crowd server must be the first directory, followed by the linked user directory. The Confluence user synchronization uses the Crowd server. User Profiles for Confluence synchronization skips the unsupported Crowd server and uses the second user directory.
-
The usernames must be exactly the same (upper/lower case) in Confluence (from Crowd) and in the linked user directory
-
Please test it first on a separate test environment.
If you have any further questions, please do not hesitate to contact us at products@elevatic.com.