Allowing OAuth access
The JIRA gadget on the 'consumer' is granted access to your JIRA data via an 'OAuth access token', which acts as a type of 'key'. As long as the consumer is in possession of this access token, the JIRA gadget will be able to access JIRA data that is both publicly available and privy to your JIRA user account. You can revoke this access token at any time from your JIRA user account, otherwise, all access tokens expire after seven days. Once the access token is revoked or has expired, the JIRA gadget will only have access to publicly available data on your JIRA instance.
An OAuth access token will only appear in your user profile if the following conditions have been met:
Your JIRA Administrator has established an application link using OAuth between your JIRA instance and the consumer. JIRA Administrators should refer to Using AppLinks to link to other applications.
- You have accessed a JIRA gadget on a consumer and have allowed this gadget access to your JIRA data. See Issuing OAuth access tokens below for details on this process.
Screenshot: Viewing your OAuth Access Tokens
Issuing OAuth access tokens
An OAuth access token is issued by JIRA to provide one of its gadgets on a consumer, access to your JIRA data (that is, data which is restricted to your JIRA user account).
- When you are using a JIRA gadget on a consumer (such as Bamboo) and this gadget requires access to your JIRA data, you will first be prompted to log in to JIRA (if you have not already done so).
- Once you have logged in to JIRA, you will be prompted with a 'Request for Access' message:
Screenshot: Request for Access Message
At this point, JIRA is preparing to issue the JIRA gadget (on the consumer) with an OAuth access token. - To grant the gadget access to your JIRA data, click the 'Approve Access' button. The consumer application will receive the OAuth access token from your JIRA instance. This access token is specific to this gadget and as long as the token resides with the gadget, your gadget will have access to your JIRA data.
Revoking OAuth access tokens
You can revoke an OAuth access token to deny a JIRA gadget on a consumer access to JIRA data which is restricted to your JIRA user account. You can only revoke OAuth access tokens that you have allowed JIRA to issue previously.
- Choose your user name at top right of the screen, then choose Profile.
- Click the 'Tools' menu and select the 'View OAuth Access Tokens' menu item.
- The 'OAuth Access Tokens' page will be displayed.
Screenshot: Viewing your OAuth Access Tokens
Your list of OAuth access tokens is presented in a tabular format, with each access token presented in separate rows and each property of these tokens presented in a separate columns. Refer to the OAuth access token table details section below for more information about this table. - Locate the JIRA gadget and its associated consumer application whose OAuth access token you wish to revoke and click its 'Revoke OAuth Access Token' link in the 'Actions' column.
- You may be prompted to confirm this action. If so, click the 'OK' button.
The gadget's access token is revoked and the JIRA gadget on the consumer will only have access to publicly available JIRA data.
OAuth access token table details
Column name | Description |
|---|---|
Consumer | The name of the JIRA gadget that was added on the consumer. |
Consumer Description | A description of this consumer application. This information would have been obtained from the consumer's own OAuth settings when an OAuth relationship was established between JIRA and that consumer. |
Issued On | The date on which the OAuth access token was issued to the consumer by JIRA. This would have occurred immediately after you approved this gadget access to your JIRA data (privy to your JIRA user account). |
Expires On | The date when the OAuth access token expires. This is seven days after the 'Issued On' date. When this date is reached, the access token will be automatically removed from this list. |
Actions | The functionality for revoking the access token. |
If the consumer is another Atlassian application, this information is obtained from the