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

Crowd - resetting passwords for users in multiple directories


We have several Confluence and JIRA instances. Some are open to our customers and all of our employees. Some open to all of our employees. Some are restricted to only a small handful of our employees.

In Crowd, we have separate user directories (Customers, Employees, Restricted), with one Confluence app connected to Customers and Employees, another connected to just Employees, and another to just Restricted.

Obviously, the Restricted directory has some of the same users that are in the Employees directory.

I'm struggling which approach to use so that any user (employee or customer) can reset their password in a connected app, especially since there is an "overlap" of users between the Employees and Restricted directories.

Option 1 - Is it best to give each application read/write permission to the directories so that the user changes their password from the Crowd-connected app?

Option 2 - Or is it best to give each application read-only permission to the directories and give users "user access" to Crowd (per so that they can go (only) to Crowd to change their password?  

I believe a deficiency of Option 2 is that Crowd only resets the password in the directory first connected to the "crowd" application in Crowd... so a user in multiple directories wouldn't be able to reset ALL of their passwords.

Thanks in advance!


1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 19, 2017

Thanks for posting this question! I am tempted to move it to the Discussion section of the forum, as it is a great talking point.

To me it seems like a better experience for the user to change the password in the application where they use the password, rather than having to go to another URL altogether. So I like option 1.

I tend to agree, but if the password is changed in Crowd, does it have to be via CrowdID to ensure that the user's password is updated in ALL directories in which they are a member?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events