
2FA login for Jira - on-premise or in the cloud. Simplicity and security combined for the best user experience and data protection
2FA login for Jira - on-premise or in the cloud. Simplicity and security combined for the best user experience and data protection
2FA login for Jira - on-premise or in the cloud. Simplicity and security combined for the best user experience and data protection
The strongest 2FA with a customizable login:
- Biometric login (FaceID and fingerprint)
- Desktop Apps (OSX / Windows 10)
- Mail 2FA
- TOTP (integration with Google, Authy or other 2FA apps)
- 2FA activation that fits your setup and requirements
- 2FA limited to specific groups
- Protect Jira Service Desk logins
- Location based 2FA configuration
- SSO Support
- Crowd or internal user management available
For cloud and self-managed Jira, with 2FA based on-premise or the cloud: it fits your setup, no matter how complex.
2FA in the cloud for an easy setup, or go on-premise for full control.
Questions? support@secsign.com
More details
Download the app (iOS or Google) and create a SecSign ID.
You can try the add-on and apps for free. More information about the Jira add-on is available here.
Strongest Protection:
Advanced elliptic curve PKI cryptography. Authentication protected with Challenge Response Authentication (2048 bit key SafeKey Procedure) or elliptic curves (TEE). No passwords or complex codes needed.
Protect all access points:
We offer 2FA plugins for most Atlassian services and for literally any other access point, including SAML and OAuth solutions. An overview of our plugins is available here
Shared User Directory:
Use your internal Jira Directory, Crowd or Active Directory to manage your users.
Selective 2FA requirements:
- Activate 2FA for user groups and limit 2FA to outside DMZ
- Mobile app-based authentication, desktop app or Email-OTP authentication for users without a smartphone.
For more information about PKI security and how to use SecSign ID visit our user guide or contact us at sales@secsign.com
Reviews for cloud
(7)Sign in to write a review


Hello Andrew,
thank you for your feedback. Unfortunately, you did not respond to our last Email. We suspect a java script error on your site to be the reason for the issue. You can contact us at support@secsign.com and we are happy to help you with some additional troubleshooting.
Sincerely,
Your SecSign Team

Hi Niek,
thank you for taking the time to review our plugin. As a matter of fact, most customers can't believe our app really offers 2FA because it's just so convenient.
But we can reassure you, it really is 2FA: In fact it is one of the strongest methods available on the market. More information about the procedure can be found here.
I understand it that you want an additional login with the Confluence/JIRA Login credentials before the two-factor authentication kicks in? With the SecSign ID the user has to confirm the login with the private key on his smartphone. Confluence/JIRA verifies the users' information with the SecSign ID server. So basically, the SecSign ID server is the third party you are referring to. However, if you insist on an additional login step with the Confluence/JIRA credentials: this is absolutely doable with our plugin if you are using an on-premise server. Feel free to contact us at sales@secsign.com with the approximate number of users and we are happy to assist you.
PKI based 2FA is extremely secure because the sensitive user data are never transmitted via the browser/app. That means no secure authentication credentials are communicated between the authentication service, Confluence and the phone. The two factors for the SecSign ID are the PIN/password (knowledge) and the private key secured on the phone (possession). It works similar to using your debit card on an ATM.
Don't hesitate to contact us with any questions you may have about the procedure.
Reviews for server
(7)Sign in to write a review
Hi Alexander,
Thank you for your feedback. We are very sorry for the inconveniences and will be happy to help you to find the error so that you can use the SecSign ID.
Usually, the redirection after the login works fine, and you are automatically redirected to the page that you had to leave for the login.Could you please send us the log files of the system to support@secsign.com, so we that we can further investigate the problem?Also, please do not hesitate to contact us, if you need any assistance on getting the log files or have any questions.
Sincerely,
Your SecSign Team




Hello Andrew,
thank you for your feedback. Unfortunately, you did not respond to our last Email. We suspect a java script error on your site to be the reason for the issue. You can contact us at support@secsign.com and we are happy to help you with some additional troubleshooting.
Sincerely,
Your SecSign Team
Reviews for Data Center
(7)Sign in to write a review


Hello Andrew,
thank you for your feedback. Unfortunately, you did not respond to our last Email. We suspect a java script error on your site to be the reason for the issue. You can contact us at support@secsign.com and we are happy to help you with some additional troubleshooting.
Sincerely,
Your SecSign Team

Hi Niek,
thank you for taking the time to review our plugin. As a matter of fact, most customers can't believe our app really offers 2FA because it's just so convenient.
But we can reassure you, it really is 2FA: In fact it is one of the strongest methods available on the market. More information about the procedure can be found here.
I understand it that you want an additional login with the Confluence/JIRA Login credentials before the two-factor authentication kicks in? With the SecSign ID the user has to confirm the login with the private key on his smartphone. Confluence/JIRA verifies the users' information with the SecSign ID server. So basically, the SecSign ID server is the third party you are referring to. However, if you insist on an additional login step with the Confluence/JIRA credentials: this is absolutely doable with our plugin if you are using an on-premise server. Feel free to contact us at sales@secsign.com with the approximate number of users and we are happy to assist you.
PKI based 2FA is extremely secure because the sensitive user data are never transmitted via the browser/app. That means no secure authentication credentials are communicated between the authentication service, Confluence and the phone. The two factors for the SecSign ID are the PIN/password (knowledge) and the private key secured on the phone (possession). It works similar to using your debit card on an ATM.
Don't hesitate to contact us with any questions you may have about the procedure.
Cloud Pricing
Server Pricing
Data Center Pricing
SecSign Technologies provides support for this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 4.6.6 • Jira Server 6.4 - 8.16.0 • Released 2021-03-12
Summary
Minor bugfixes
Details
- The TOTP login won't show a back button incorrectly
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Two-Factor Authentication (2FA) for Jira via search. Results include app versions compatible with your Jira instance.
- Click Install to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
To find older Two-Factor Authentication (2FA) for Jira versions compatible with your instance, you can look through our version history page.