Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
AnnWorley Atlassian Team 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
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

173 views 0 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you