Adaptive Insights

I am not using this connector currently, but the Domo support pages indicates need for a ClientID, obtained after registering a Workday API Client. And it should have a token endpoint.

In general, a JWT (JSON Web Token) is used as a form of authentication when connecting to APIs or services, including when using connectors like the Adaptive Insights Connector in Domo.

Here's how the process typically works:

1. Generate JWT Token: The user or application generates a JWT token that includes information about the user and other relevant details.
2. Include Token in API Request: When making API requests to a service like Adaptive Insights, the JWT token is included in the request headers. This token serves as a form of authentication, proving that the requester has the necessary permissions.

If you are receiving an error stating that the JWT token is not correct, it indicates that there might be an issue with the token itself or it can't find one. Here are some common reasons for such errors:

• Incorrect Token: The token might be generated incorrectly or might have expired.
• Mismatched Secret: The token is typically signed with a secret key. If there is a mismatch between the key used to sign the token and the key expected by the service, authentication will fail.
• Token Expiry: JWT tokens often have a limited lifespan. If the token has expired, it will no longer be valid for authentication.
• Token Format: Ensure that the token is formatted correctly according to the specifications required by the Adaptive Insights Connector.