You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some environments, the access token is obtained by passing the user and password to a custom REST API.
The purpose of this request is to enable the inventory plugin to also work when the authentication is done in this 2 step approach.
Step 1: When a new field is present ( suggested name: token_uri, envvar: SN_TOKEN_URI), a call is made to the URI using basic authentication and an access token is obtained
Step 2: The access token is then used by the inventory plugin to connect to ServiceNow
ISSUE TYPE
Feature Idea
COMPONENT NAME
Inventory plugin.
ADDITIONAL INFORMATION
The text was updated successfully, but these errors were encountered:
AAP uses the inventory plugin from servicenow.itsm to read CMDB data from ServiceNow:
Standard authentication methods always worked for this (user/password)
Custom method is being requested as a new feature, because the customer has a proprietary method for generating their access tokens.
This issue is a request to allow such tokens to be obtained, when optional fields like the URL for the external call is passed, and then used in the remaining of the inventory logic.
The customer has even implemented the solution for this, but Tim was going to check if adding this feature to the collection would be allowed, as this is not applicable for all users.
SUMMARY
In some environments, the access token is obtained by passing the user and password to a custom REST API.
The purpose of this request is to enable the inventory plugin to also work when the authentication is done in this 2 step approach.
ISSUE TYPE
COMPONENT NAME
Inventory plugin.
ADDITIONAL INFORMATION
The text was updated successfully, but these errors were encountered: