-
Suggestion
-
Resolution: Unresolved
-
None
-
4
-
4
-
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...
- relates to
-
- Gathering Interest
- links to
- mentioned in
-
Page Failed to load
[JSDSERVER-7295] Insight Imports to support other than Basic Authentication
Jira REST API imports should be authorized by personal tokens 
native Jira rest on self data.
Would be extremely useful, for me personally I've had AD account lockouts if I've gone in to edit an import config and I might have the old or wrong password autofilling the password field. Everything else we have is using oauth so would be great if we could leverage our existing oauth connections to Gitlab and Bitbucket
Please this feature is mandatory to integrate different systems
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!