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

Password expiration

I know this question has been asked a lot. However, I'd like to know how other JIRA admins are dealing with the issue ...

My company has a policy of expiring passwords after 90 days. We're using Crowd as user directory to JIRA (v6.3).

Whenever a user's password has expired JIRA will simply reject the user's credentials. There's no hint that the password has expired and needs to be changed. Most other applications will show a form to force a password change - even Crowd does so, but JIRA doesn't.

This behaviour is a major impact to our JIRA's user acceptance. Although most people know that they simply have to click the "I forgot my password" link, it's always a cause for confusion and upset. I'm aware that there are some add-ons and scripts around that will notify users about password expiry. However, I'd like to refrain from adding third party add-ons and scripts as I've encountered compatibility issues in the past.

So, how are you dealing with password expiry at your company's JIRA?





2 answers


I am sure that there are more solutions to this problem that you can count.  I have faces this most places I have worked.  Currently, the best solution I have used is to connect JIRA to Microsoft Active Directory.  The same MS AD instance that is used by the organization to log into their computer.  The passwords rules and management are then pushed to MS AD and you don't have to worry about expiring passwords, password rules, password complexities, and such.  The only downside is that some users will attempt to change their password via JIRA thinking that JIRA will change it and it does not if you set it up the way I have.  JIRA simply uses MS AD for authentication, nothing more.





Integrate with AD is good for password policy but this issue still happens with Local/Service account as these account used by JIRA automation.

+1 We have exactly the same problems!

I found a feature request here:

And also I found this Plugin but I´m not sure if this plugin will support an external user directory as well.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

275 views 8 7
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