Your own ID-Server
On premise installations of SecSign ID offer the flexibility to connect with your preferred servers, services, and devices. And you can customize the SecSign ID with your own organization’s branding.Learn More
The following tutorial describes the configuration to use Two-Factor Authentication with SecSign ID Plugin on a third party application using Jira REST API
JIRA is a web application for operational project management as well as for error management and troubleshooting. There are many 3rd party apps available, which can access Jira, to post, update or modify content. Many companies maintain their own on-premise solutions, to access Jira data in their own applications.
Those 3rd party applications use the Jira REST API to exchange information. The following tutorial describes why you should set up OAuth with SecSignID to secure your Jira REST API.
SecSign ID is a plugin for real two-factor authentication (2FA) for Jira. 2FA adds another layer of security to your installation by using a second token. In this case the physical token is your smartphone.
The Jira REST API is the primary way to interact with Jira remotely, whether you are building an app, scripting interactions with Jira or developing any other integration:
If you are integrating directly with the Jira Cloud REST APIs it is recommended to use OAuth authentication method. The OAuth authorization framework enables a third-party application to obtain limited access to Jira resources. The third-party apps won’t store protected data like user passwords or credentials. OAuth is the recommended way to authenticate users to the Jira REST API. Read more about OAuth and SecSignID
For implementations with low security requirements, such as scripts and bots, it is possible to use Basic authentication method. It utilizes just plain old user credentials with name and password. Those credentials are transmitted in plain text and pose a security risk.
A great starting guide to the Jira REST API with OAuth authentication is described in the Jira Developer Tutorial:
After Jira was set up properly, you have to register your 3rd party application under Administration > Applications > Application links.
Your client will require the following URLs to be able to make authentication requests to JIRA:
|request token url||JIRA_BASE_URL + /plugins/servlet/oauth/request-token|
|authorization url||JIRA_BASE_URL + /plugins/servlet/oauth/authorize|
|access token url||JIRA_BASE_URL + /plugins/servlet/oauth/access-token|
The third-party app or client can be in whatever language you prefer, it just needs to implement the OAuth protocol. OAuth offers a collection of libraries and services that support OAuth 2.0 for common languages like Java, Php, Swift, Python, Ruby and so on.
At the moment Oauth 2.0 is only available for Atlassian Connect add-ons. For REST API calls, only Oauth is supported.
SecSignID Plugin needs to be installed in your Jira instance. Follow the instructions to set up SecSignID in Jira:
Refer to the Jira Tutorial OAuth on how to obtain a request token with the example client. After obtaining the request token from JIRA, you will get the access URL. The user needs to open the URL, in a browser or internal web view, to authenticate with Jira. If the SecSignID plugin is set up correctly, your users will be able to authenticate via their SecSignID.
Jira will ask, if you give the third-party app the permission to read and write content under your account. After approving the access, Jira will confirm that you have successfully authorized the access. It gives a verification code which you’ll need to get the access token like described in the Jira Tutorial.
Die 2FA von SecSign ist die stärkste Zwei-Faktor-Authentifizierung auf dem Markt! Profitieren Sie von unbegrenzten Möglichkeiten der Integration. Für so gut wie jedes Login bietet SecSign eine Absicherung. Auch für komnplizierte Nutzermanagement-Situationen, wie beispielse Nutzer in und außerhalb eines AD hat SecSign unkomplizierte Lösungen parat.
We are happy to announce that the SecSign ID server has passed the official FIDO certification program of the FIDO Alliance. This will allow you to use the complete FIDO2/WebAuthn standard for passwordless 2FA sign-ins in your exi ...Mehr Lesen
The FIDO2 Project is a set of standards developed by the FIDO Alliance and the World Wide Web Consortium (W3C) to create a strong authentication protocol for the web. It consist mainly of the WebAuth standard for the browser part ...Mehr Lesen
In the recent weeks, home office work has increased potentially. And while employees are practicing social distancing from their home computer, attackers are working hard to exploit security issues in this situation that is unfami ...Mehr Lesen
Want to learn more about SecSign’s innovative and highly secure
solutions for protecting your user accounts and sensitive data?
Use our contact form to submit your information, and a SecSign sales representative will contact you within one business day.
If you need assistance with an existing SecSign account or product
installation, please see the FAQs for more information on the most common questions. You don’t find the solution to your problem? Don’t hesitate to contact the
I am Interested in