-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
1
-
Problem Definition
Currently Assets JSON importer only supports basic authentication. As enterprise applications moving away from basic auth it's becoming a compatibility issue between Jira (Assets) and external sources
Suggested Solution
Introduce Token based authentication for JSON import
Workaround
- Create the http call to the target host which needs token based authentication
- Save the response as a file JSON
- import the file
You can create a service in between Jira and target host and automate this process as well.
- is cloned from
-
JSDSERVER-7294 Add ability to authenticate JSON import though API token
- Gathering Interest
- relates to
-
JSDCLOUD-12097 Custom header in JSON import
- Closed
-
JSDCLOUD-12094 Add ability to have custom headers in JSON import
- Gathering Interest
-
JSDCLOUD-12095 Allow using API token authentication in Assets JSON importer settings
- Gathering Interest
[JSDCLOUD-12096] Add ability to authenticate JSON import through API token
Support reference count | New: 1 |
UIS | Original: 1 | New: 0 |
Summary | Original: Add ability to authenticate JSON import though API token | New: Add ability to authenticate JSON import through API token |
Link |
New:
This issue relates to |
Link | New: This issue relates to JSDCLOUD-12095 [ JSDCLOUD-12095 ] |
Link | New: This issue relates to JSDCLOUD-12094 [ JSDCLOUD-12094 ] |
Description |
Original:
h3. Problem Definition
Currently Insight JSON importer only supports basic authentication. As enterprise applications moving away from basic auth it's becoming a compatibility issue between Jira (Insight) and external sources h3. Suggested Solution Introduce Token based authentication for JSON import h3. Workaround * Create the http call to the target host which needs token based authentication * Save the response as a file JSON * import the file You can create a service in between Jira and target host and automate this process as well. |
New:
h3. Problem Definition
Currently Assets JSON importer only supports basic authentication. As enterprise applications moving away from basic auth it's becoming a compatibility issue between Jira (Assets) and external sources h3. Suggested Solution Introduce Token based authentication for JSON import h3. Workaround * Create the http call to the target host which needs token based authentication * Save the response as a file JSON * import the file You can create a service in between Jira and target host and automate this process as well. |
Component/s | Original: Assets - Core experiences [ 63613 ] | |
Component/s | New: Assets - Import [ 63706 ] | |
Key | Original: JSDSERVER-12261 | New: JSDCLOUD-12096 |
Project | Original: Jira Service Management Server and Data Center [ 15611 ] | New: Jira Service Management Cloud [ 18512 ] |
Link | New: This issue is cloned from JSDSERVER-7294 [ JSDSERVER-7294 ] |