• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Assets - Import
    • None
    • 0
    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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.

            [JSDCLOUD-12096] Add ability to authenticate JSON import through API token

            SET Analytics Bot made changes -
            Support reference count New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            Angélica Luz made changes -
            Summary Original: Add ability to authenticate JSON import though API token New: Add ability to authenticate JSON import through API token
            Angélica Luz made changes -
            Link New: This issue relates to JSDCLOUD-12097 [ JSDCLOUD-12097 ]
            Angélica Luz made changes -
            Link New: This issue relates to JSDCLOUD-12095 [ JSDCLOUD-12095 ]
            Angélica Luz made changes -
            Link New: This issue relates to JSDCLOUD-12094 [ JSDCLOUD-12094 ]
            Angélica Luz made changes -
            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.
            Angélica Luz made changes -
            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 ]
            Angélica Luz made changes -
            Link New: This issue is cloned from JSDSERVER-7294 [ JSDSERVER-7294 ]
            Angélica Luz created issue -

              Unassigned Unassigned
              smitra2@atlassian.com Suddha
              Votes:
              5 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: