You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Less and less companies are enforcing password expiration dates these days. Instead, 2FA is increasingly more popular.
This is very easy to setup with Access if you’re on Cloud, but not obvious for on-prem.
There are basically two approaches that you can take if you want to add second factor authentication to Jira, Confluence, or any other Server / Data Center application:
If you’re already using a commercial Identity Provider, it will probably give you some options for Multi-Factor Authentication. Heck, you can even go passwordless these days with the right setup.
Passwords are just an authentication option in Okta's MFA policies
Here are some useful links:
To add Atlassian apps into your IdP you will need to add a SAML SSO marketplace app. The the most widely installed and reviewed is resolution’s SAML SSO for Jira. (For full disclosure, resolution GmbH is my current employer)
You can also configure 2FA by adding an app from the marketplace. This might be interesting if your company only uses one Atlassian product or if for some reason you don’t want to set up a company-wide setting in your IdP.
Note that, in this case, you will have to install one 2FA app per each Atlassian application.
There are many options in the marketplace. We have personally tested Syracom’s 2FA for Jira, and it’s compatible with our SSO app.
Inbound Marketing | Thought Leadership
19 accepted answers