Basically you can use User Profiles for Confluence with Crowd, but there is a catch: The synchronization feature of User Profles for Confluence does only support directly connected LDAP-based directories, like Active Directory.

So, what will work?

• You can add new profile elements.
• Fields can be /wiki/spaces/upp/pages/9414235.

• /wiki/spaces/upp/pages/9414235 within Confluence.

• Use User Profles for Confluence /wiki/spaces/upp/pages/9414235.

And what won't?

• Synchronizing data from any directory which 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

The ability to synchronize User Profles for Confluence with Crowd is not currently supported but there is a workaround 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:https://confluence.atlassian.com/display/DOC/Configuring+User+Directories).

There are several constraints for this scenario:

1. The order of the directories in the configuration is important. The Crowd server must be the first directory and then the linked user directory as second. The Confluence user synchronization uses the Crowd server. User Profles for Confluence synchronization skips the unsupported Crowd server and uses the second user directory.
2. The usernames must be exactly the same (upper/lower case) in Confluence (from Crowd) and in the linked user directory
3. Please test it first on a separate test environment.

If you have any further questions, please do not hesitate to contact us at products@communardo.de.