Snowflake database connection with Splunk DB Connect using PAT authentication

Available Languages

Updated:October 1, 2026
Document ID:SPLK052338

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Apps & Add-ons Splunk DB Connect Splunk Enterprise Splunk Cloud

Description

This article provides information on connecting Snowflake with Splunk DB Connect using PAT authentication.


Investigation

Splunk DB Connect supports connecting to Snowflake with RSA authentication or with a user ID and password. An additional option is now available: programmatic access token (PAT) authentication.


Resolution

Follow the steps below to configure a Snowflake connection in Splunk DB Connect using a PAT:

  1. In Snowflake, generate a programmatic access token:

    • Navigate to Admin > User & Roles > [Select User] > Programmatic access tokens > Generate new token.

    • Ensure a network policy is associated with the user.

  2. In Splunk DB Connect, add the token as a password for the Snowflake identity.

  3. Configure the Snowflake connection in Splunk DB Connect using the generated token.

Warning: After the token expires, the connection to Snowflake will be lost.

Note:- This information will be published in the documentation for version 4.1.0.


For additional details, refer to Configuring the JDBC Driver > Authenticating with a Programmatic Access Token.

Revision History

Revision Publish Date Comments
1.0
01-Oct-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products