Summary
Users facing ‘invalid JWT’ token errors after upgrading Snowflake destination connector to V2/V3. Seeking input on similar experiences or if specific to user’s environment.
Question
Has anyone ran into authentication problems with a Snowflake destination after upgrading to either V2 or V3 of the Snowflake destination connector? I’m getting “invalid JWT” token errors when using the exact same setup that I used previously with V1 connectors, and am wondering if anyone else has seen something similar, or if this is specific to my environment
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.