Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to best preserve existing Confluence, when integrating with new Jira, AD users managed by crowd

I am trying to set up crowd 2.12.2 so that it manages users both for a brand new Jira 7.4, and an existing Confluence 5.10.2 installation.

The Confluence installation have up until now managed its own users.

I would like to preserve as much of the existing Confluence strucure as possible, while at the same time integrating the Confluence installation with Jira.

Is there a good way to map existing Confluence users to AD users?


Failing that: is there a good way to transfer ownership of pages and spaces from the Confluence users to the equivalent AD users?


1 answer

0 votes
AnnWorley Atlassian Team Aug 11, 2017

An application link that integrates JIRA and Confluence will not change your Confluence structure, so we are good there. It is possible to use JIRA for user management for Confluence, but you mention you will be using Crowd.

The AD directory will be created in Crowd, then, if the AD users have the same usernames, Confluence will "see" them as the same users, so the permissions in Confluence will be fine. If they have a different username in AD, you can use aliasing within Crowd to continue logging into Confluence with the same usernames: Specifying a User's Aliases

If you don't need aliasing or Single Sign-on you may want to connect JIRA and Confluence each directly to AD as in these docs:

JIRA - Connecting to an LDAP directory

Confluence - Connecting to an LDAP directory

I look forward to any follow up questions.

Hi and thanks for your answer

The Confluence installation had 41 active users with usernames matching their AD usernames, and 101 active users with usernames not matching their AD usernames.

Based on Effective memberships with multiple directories we made an initial plan to:

  1. Manage Jira with a delegated directory, with locally managed groups, using lazy synchronization of users, with initial membership in the group jira-users
  2. Rename the usernames of the 101 users that have a different username than their AD user, to get a username that matches their AD user
  3. Import the Confluence users and groups into a crowd directory
  4. Set up Confluence to be managed by both the same delegated directory as Jira, as well as the imported Confluence directory, aggregating users (and maybe groups)

Hopefully this will give us a Confluence and Jira working nicely together, while at the same time preserving the history and ownership of the existing Confluence pages...?

Initially we will start by managing just Jira with crowd using the delegated directory, and once that's up and running we will decide where we go from there.

An additional bit of information: Single SignOn is a requirement of whatever solution we end up with.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events