Generate SolarWinds OAuth Tokens

To connect SolarWinds to a Knowledge Hub knowledge base, you must either provide your SolarWinds credentials to NiCE Professional Services or enter them in Knowledge Hub yourself. This page describes how to generate and manage JWT (JSON Web Token) in the SolarWinds interface. The JWT method is a token-based method that enables SolarWinds to request and use access tokens for secure communication with Knowledge Hub.

Prerequisite for Generating the JW Token

  • You must have a Service Desk Administrator license within the SolarWinds Service Desk.

  • Only administrators with full application access can create tokens.

  • Users can only create tokens for themselves.

Creating the JW Token

  1. In the SolarWinds Service Desk interface, go to Setup > Users & Groups > Users.

  2. In the Allowed Domains tab, locate your own user detail page (not the profile card).

  3. Click the username. The system displays the user detail page.

  4. From the Actions dropdown menu, click Generate JSON Web Token.

    This option is available only if you have Service Desk Administrator rights.

  5. Once generated, the JSON Web Token section appears with these options:

    1. Copy: Copy the token to clipboard.

    2. Reset: Generate a new token (invalidates the previous one).

    3. Delete: Remove your token completely.

    4. Hide Token: Minimize the token display.

Appflow Configuration

This configuration is used to establish a secure connection between SolarWinds and AWS AppFlow. This JSON structure defines what data to pull and from where.

{

"SOLARWINDS_BASE_URL": "",

"SOLARWINDS_OBJECT_NAME": "",

"SOLARWINDS_JWT_TOKEN": ""

}

Sample JSON Structure

{

"SOLARWINDS_BASE_URL": "https://your-instance.solarwinds.com",

"SOLARWINDS_OBJECT_NAME": "incident",

"SOLARWINDS_JWT_TOKEN": "your-generated-token"

}

When all the fields are correctly configured AppFlow acts as a data pipeline. It transforms and transfers data from SolarWinds to S3. Thereafter, Knowledge Hub consumes the data from S3.

Access Token Expiration

Category

Condition

<IMPACT on token>
Token Validity Active User Account Token is disabled if the user is disabled.
  Permission Changes Token permissions change to match the user's updated role.
  Token Reset Impact Resetting or deleting the token breaks any API connection using that token.
Token Expiration No built-in expiration Token remains valid indefinitely unless manually reset, deleted, or user loses admin rights.
  Manual Reset or Deletion Invalidates the existing token.
  Loss of Admin Privileges Token becomes invalid.
Invalidation Events Manual Reset All previously generated tokens become invalid.