Splunk DB Connect: Snowflake Connection Error - "Unable to Save Due to JWT Token Invalid Issue"

Applicability

Description

Encounter the following errors when attempting to save a Snowflake connection in Splunk DB Connect: "JWT Token is Invalid."

The issue typically arises when creating a Snowflake connection and trying to save it, with the second error being related to an invalid JWT Token caused by a time synchronization issue between systems.

Investigation

After generating a new key, the connection could not be saved due to the error message: "JWT Token is Invalid."

This error usually indicates an issue with the validity of the JWT Token.

Please refer to the below screenshot for reference: 

Upon further investigation, the root cause was identified as a time synchronization issue (clock skew) on the Splunk server running the Splunk DB Connect App.

The error message "JWT_TOKEN_INVALID_ISSUE_TIME" pointed to the time discrepancy.

Resolution

To resolve the issue, the following steps should be taken:

1. Verify and Correct Time Synchronization:

   • The time on the Splunk server should be synchronized correctly with the system time. Time discrepancies between the server and system can lead to JWT token issues.

2. Re-attempt Saving the Connection:

   • Once the time synchronization issue is resolved, the Snowflake connection should be saved successfully without any further errors.

Related Links

• Snowflake Documentation
• JWT_TOKEN_INVALID_ISSUE_TIME