BMC Helix ITSM Prerequisites¶
To use the BMC Helix ITSM connector with OAuth 2.0 authentication, the BMC SaaS Operations team must have set up an OAuth 2.0 application and provided you with the values you will need for generating a refresh token and bearer token.
These instructions require the use of a third-party tool such as Postman.
Obtain a Custom API URL¶
To obtain a refresh token and bearer token, you must use an API Manager Custom API URL. For information on configuring a Custom API and obtaining its URL, see these resources:
Follow these steps to obtain the refresh token and bearer token:
Obtain these values from the BMC SaaS Operations team:
- Callback URL
- Auth URL
- Access Token URL
- Client ID
- Client Secret
In Postman open a new request.
Click the Authorization tab, and use the Type menu to select OAuth 2.0.
In the Configure New Token section, configure these fields:
Field Description Token Name Enter a name for the token. Grant Type From the menu, select Authorization Code. Callback URL Enter the Custom API URL (provided by the BMC SaaS Operations team). Auth URL Enter the BMC Helix auth URL (provided by the BMC SaaS Operations team) in this format:
Access Token URL Enter the BMC Helix access token URL (provided by the BMC SaaS Operations team) in this format:
Client ID Enter your client ID (provided by the BMC SaaS Operations team). Client Secret Enter your client secret (provided by the BMC SaaS Operations team). Scope Leave this field empty. State Leave this field empty. Client Authentication From the menu, select Send as Basic Auth header.
Click Get New Access Token.
In the BMC Helix single sign-on login dialog, enter the credentials that BMC has provided.
expires_invalues returned in the response as they are to be used during connection configuration.
Contact the BMC SaaS Operations team to extend the expiration time of the bearer token.