API Token Authentication for Jira expand connection security

API Token Authentication for Jira expand connection security

Vendor: resolution Reichert Network Solutions GmbH | Key: de.resolution.apitokenauth.jira

jira server datacenter

Use API Tokens instead of username & password for your API calls. It solves challenges in Single Sign-On environments. You can disable all basic authentication & have multiple API tokens per user that can be restricted or revoked individually.

View on Marketplace
Versions (36) - Last 1 Year, Server/Data Center Only
Version Build Release Date Compatibility Hosting Status Actions Description
2.7.7-p8 2026011431001 2026-01-14 Jira Data Center 11.0.0 - 11.3.1 datacenter Pending
Release Notes:

Compatibility release for Jira 11
2.7.7-p8 2026011430001 2026-01-14 Jira Server 11.0.0 - 11.3.1 server Pending
Release Notes:

Compatibility release for Jira 11
2.7.7 2025093031001 2025-09-30 Jira Data Center 8.19.0 - 10.7.4 datacenter Pending
Release Notes:
  • Updated 3rd-party libraries
2.7.7 2025093030001 2025-09-30 Jira Server 8.19.0 - 10.7.4 server Pending
Release Notes:
  • Updated 3rd-party libraries
2.7.5 2025061731001 2025-06-17 Jira Data Center 8.19.0 - 10.7.4 datacenter Pending
Release Notes:
  • Allowing servicedesk customers to create tokens via REST, provided the permissions in the app allow that
  • 3rd-party and internal library updates
2.7.5 2025061730001 2025-06-17 Jira Server 8.19.0 - 10.7.4 server Pending
Release Notes:
  • Allowing servicedesk customers to create tokens via REST, provided the permissions in the app allow that
  • 3rd-party and internal library updates
2.7.4 2025041431001 2025-04-14 Jira Data Center 8.19.0 - 10.7.2 datacenter Pending
Release Notes:
  • Fixed a bug that caused the Jira session endpoint to return HTTP 500 if the user trying to authenticate doesn't exist
  • Updated an internal library
2.7.4 2025041430001 2025-04-14 Jira Server 8.19.0 - 10.7.2 server Pending
Release Notes:
  • Fixed a bug that caused the Jira session endpoint to return HTTP 500 if the user trying to authenticate doesn't exist
  • Updated an internal library
2.7.3 2025031031001 2025-03-10 Jira Data Center 8.19.0 - 10.4.1 datacenter Pending
Release Notes:

Added values of 1 to 4 minutes to the "Maximum/ Rate Limit Bucket Lifetime" option.
2.7.3 2025031030001 2025-03-10 Jira Server 8.19.0 - 10.4.1 server Pending
Release Notes:

Added values of 1 to 4 minutes to the "Maximum/ Rate Limit Bucket Lifetime" option.
2.7.2 2024110431001 2024-11-04 Jira Data Center 8.12.0 - 10.4.1 datacenter Pending —
2.7.2 2024110430001 2024-11-04 Jira Server 8.12.0 - 10.4.1 server Pending —
2.7.1 2024082631001 2024-08-26 Jira Data Center 8.12.0 - 10.1.1 datacenter Pending
Release Notes:

Jira 10 Compatibility Release

2.7.1 2024082630001 2024-08-26 Jira Server 8.12.0 - 10.1.1 server Pending
Release Notes:

Jira 10 Compatibility Release

2.6.1 2024070231001 2024-07-02 Jira Data Center 8.12.0 - 9.17.3 datacenter Pending
Release Notes:

A new option in the System-Wide settings allows admins to control how often the 'Last Used' value of a token is being updated. Read here for more details.

2.6.1 2024070230001 2024-07-02 Jira Server 8.12.0 - 9.17.3 server Pending
Release Notes:

A new option in the System-Wide settings allows admins to control how often the 'Last Used' value of a token is being updated. Read here for more details.

2.6.0 2024050631001 2024-05-06 Jira Data Center 8.12.0 - 9.16.1 datacenter Pending
Release Notes:
  • To be prepared for upcoming changes in the Atlassian audit-logging service we refactored the app's code accordingly and improved how details of events are being tracked
  • Fixed a bug causing broken links to the Atlassian application (i.e. the audit log) in our UI whenever the instance was using an application context path
2.5.3 2024050621001 2024-05-06 Jira Data Center 8.5.0 - 9.15.2 datacenter Pending
Release Notes:
  • Fixed a bug introduced with version 2.5.0 that caused HTTP status code 403 responses when using API Tokens with Basic Authentication whenever "Disable Basic Authentication with User Password" was enabled in "System-Wide Settings"
  • 3rd-Party Library Updates
2.6.0 2024050630001 2024-05-06 Jira Server 8.12.0 - 9.16.1 server Pending
Release Notes:
  • To be prepared for upcoming changes in the Atlassian audit-logging service we refactored the app's code accordingly and improved how details of events are being tracked
  • Fixed a bug causing broken links to the Atlassian application (i.e. the audit log) in our UI whenever the instance was using an application context path
2.5.3 2024050620001 2024-05-06 Jira Server 8.5.0 - 9.15.2 server Pending
Release Notes:
  • Fixed a bug introduced with version 2.5.0 that caused HTTP status code 403 responses when using API Tokens with Basic Authentication whenever "Disable Basic Authentication with User Password" was enabled in "System-Wide Settings"
  • 3rd-Party Library Updates
2.5.2 2024012221001 2024-01-22 Jira Data Center 8.5.0 - 9.15.2 datacenter Pending
Release Notes:

Fixed an issue causing log file messages about an error while extracting the user key.

2.5.2 2024012220001 2024-01-22 Jira Server 8.5.0 - 9.15.2 server Pending
Release Notes:

Fixed an issue causing log file messages about an error while extracting the user key.

2.5.0 202309251001 2023-09-25 Jira Data Center 8.5.0 - 9.12.7 datacenter Pending
Release Notes:
  • Added an option to allow Basic Authentication on all endpoints/ paths; read more about it here
  • Optimised app configuration processing for performance
2.5.0 202309250001 2023-09-25 Jira Server 8.5.0 - 9.12.7 server Pending
Release Notes:
  • Added an option to allow Basic Authentication on all endpoints/ paths; read more about it here
  • Optimised app configuration processing for performance

2.4.1 202309121001 2023-09-12 Jira Data Center 8.5.0 - 9.11.3 datacenter Pending
Release Notes:

Fixed a bug preventing a successful Bearer Authentication with other authenticators even if they were still allowed.

2.4.1 202309120001 2023-09-12 Jira Server 8.5.0 - 9.11.3 server Pending
Release Notes:

Fixed a bug preventing a successful Bearer Authentication with other authenticators even if they were still allowed.

2.4.0 202309071001 2023-09-07 Jira Data Center 8.5.0 - 9.11.3 datacenter Pending
Release Notes:

Please refer to the release notes for more details.

2.4.0 202309070001 2023-09-07 Jira Server 8.5.0 - 9.11.3 server Pending
Release Notes:

Please referr to the release notes for more details.

2.3.1 202308141001 2023-08-14 Jira Data Center 8.5.0 - 9.11.3 datacenter Pending
Release Notes:

Updated OkHttp and Okio libraries

2.3.1 202308140001 2023-08-14 Jira Server 8.5.0 - 9.11.3 server Pending
Release Notes:

Updated OkHttp and Okio libraries

2.3.0 202307171001 2023-07-17 Jira Data Center 8.5.0 - 9.10.2 datacenter Pending
Release Notes:

Added configuration option to limit the number of maximum active tokens a user can have at a time. Read more about it in our documentation.

2.3.0 202307170001 2023-07-17 Jira Server 8.5.0 - 9.10.2 server Pending
Release Notes:

Added configuration option to limit the number of maximum active tokens a user can have at a time. Read more about it in our documentation.

2.2.4 202302270001 2023-02-27 Jira Data Center 8.5.0 - 9.9.2 datacenter Pending
Release Notes:

Added log file entry in case Bearer Authentication with a token fails. Please be aware that these failures are currently not audit-logged. We'll add this soon in an upcoming release.

2.2.4 202302271001 2023-02-27 Jira Server 8.5.0 - 9.9.2 server Pending
Release Notes:

Added log file entry in case Bearer Authentication with a token fails. Please be aware that these failures are currently not audit-logged. We'll add this soon in an upcoming release.

2.2.3 202302140001 2023-02-14 Jira Data Center 8.5.0 - 9.6.0 datacenter Pending
Release Notes:

Fixed a bug affecting the log file entries for tokens deleted on behalf of another user. The records mentioned the wrong user key. The audit log was not affected by that bug.

2.2.3 202302141001 2023-02-14 Jira Server 8.5.0 - 9.6.0 server Pending
Release Notes:

Fixed a bug affecting the log file entries for tokens deleted on behalf of another user. The records mentioned the wrong user key. The audit log was not affected by that bug.