Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-7295

Insight Imports to support other than Basic Authentication

XMLWordPrintable

    • 4
    • 4
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Insight Asset Management ships with some Import types, for example: JSON and DB imports.

      We have several requests to allow additional Authentication Methods to connect to the Import Source, for example:

      Configure an MSSQL Database Import with Windows Kerberos Authentication - as customers report Security will not allow for Native SQL User to be used.

      Configure a JSON Import, with Bearer Token Authentication

      See also: Mindville backlog.

      the Insight SCCM Integration Import does support 3 Authentication methods...

            [JSDSERVER-7295] Insight Imports to support other than Basic Authentication

            SET Analytics Bot made changes -
            Support reference count New: 4

            Gaëtan Mougel added a comment -

            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!

             

            Gaëtan Mougel added a comment - 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!  
            SET Analytics Bot made changes -
            UIS Original: 3 New: 4
            Marc Dacanay made changes -
            Labels New: ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 976988 ]
            SET Analytics Bot made changes -
            UIS Original: 6 New: 3
            SET Analytics Bot made changes -
            UIS Original: 3 New: 6

            Richard Bariny added a comment -

            Jira REST API imports should be authorized by personal tokens  

            native Jira rest on self data.

            Richard Bariny added a comment - Jira REST API imports should be authorized by personal tokens   native Jira rest on self data.
            SET Analytics Bot made changes -
            UIS Original: 6 New: 3
            SET Analytics Bot made changes -
            UIS Original: 3 New: 6

              Unassigned Unassigned
              8cdc82c96fd5 Yinon Negev
              Votes:
              21 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: