-
Suggestion
-
Resolution: Fixed
-
106
-
11
-
Hi everyone, with the upcoming EOS for Connect, we are focussing our efforts on Forge and continuing to bolster our APIs. With that in mind, we will not be investing into further JWT enhancements. We appreciate your support and hope your transition to Forge will be successful.
August 2024
We are currently investigating the addition of Connect_JWT to requests coming via api.atlassian.com. We will update this ticket as soon as we have an update.
Update as of June 2024
Hi everyone! I'm pleased to announce that - on top of the previously announced Oauth2.0 authentication for Forge - we now have completed the work to add JWT authentication for Assets APIs. https://developer.atlassian.com/cloud/assets/imports-rest-api-guide/authorization/
We will close this ticket now, but pease let us know if any questions or issues.
Issue Summary
As mentioned in the https://developer.atlassian.com/cloud/assets/intro/introduction-and-basics/#authentication-and-authorization documentation page, only Basic auth for REST APIs is currently supported.
As per: Security requirements for cloud applications , app developers need a temporary waiver in order to use API token authentication with Insight as it is not supported by Forge and Connect.
- relates to
-
JSDCLOUD-16715 Add support to Assets related scopes when creating an API token with scopes
- Gathering Interest
-
ACJIRA-2568 Loading...
-
ECOHELP-15223 Loading...
-
FRGE-746 Loading...
- is duplicated by
-
FRGE-1172 Loading...
- is resolved by
-
COMMIT-4586 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...