-
Suggestion
-
Resolution: Unresolved
-
None
-
11
-
9
-
While setting up Insight JSON import only basic authentication is supported.
It would be very helpful to allow/implement API token authentication as an additional option.
- is related to
-
JSDSERVER-7207 Add ability to have custom headers in JSON import
- Gathering Interest
-
JSDSERVER-7294 Add ability to authenticate JSON import though API token
- Gathering Interest
-
JSDSERVER-7295 Insight Imports to support other than Basic Authentication
- Gathering Interest
-
JSDSERVER-7453 Custom header in JSON import
- Gathering Interest
-
JSDSERVER-8005 JSON API Authenticatin
- Gathering Interest
- was cloned as
-
JSDCLOUD-12095 Allow using API token authentication in Assets JSON importer settings
- Gathering Interest
- links to
Form Name |
---|
[JSDSERVER-7236] allow using API token authentication in Insight JSON importer settings
Support reference count | New: 9 |
UIS | Original: 5 | New: 11 |
UIS | Original: 4 | New: 5 |
Labels | New: ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 976976 ] |
UIS | Original: 9 | New: 4 |
UIS | Original: 13 | New: 9 |
In order to use Assets imports, we have to allow Basic auth on API calls, which goes against Atlassian's own guidlines:
On the "Authentication methods" page of Jira itself:
But also here: Basic auth for REST APIs
JSM and Assets are both aimed at enterprise customers, basic auth just won't cut it anymore for these kinds of customers (me included).
Atlassian went through the trouble of creating PAT's specifically to stop the use of Basic Auth... Allow us to use it!
Going the extra mile and allowing OAuth or User-context tokens would be fantastic, but already allowing simple api keys / bearer tokens would be a fantastic start!