Skip to main content
Solved

Important Notice: Snowflake Deprecating Password Logins — Potential Impact on Moveworks Snowflake Integrations

  • November 27, 2025
  • 2 replies
  • 78 views

Forum|alt.badge.img+3

Sharing an important update for everyone using the Snowflake Dynamic Query / Snowflake Cortex Analyst plugin.

Snowflake has announced that they are deprecating single-factor password sign-ins, including for service accounts. Once this enforcement begins, password-only authentication will stop working, and Snowflake will require MFA or non-password mechanisms for programmatic access.

Reference:

🔗 https://docs.snowflake.com/en/user-guide/security-mfa-rollout 

 

Our Snowflake connectors today are set up using username + password. If these connectors remain unchanged, they may start failing with authentication errors when Snowflake completes this rollout.

 

Snowflake recommends migrating to one of the supported authentication methods for automated integrations:

Key-pair authentication (public/private key)

🔗 https://docs.snowflake.com/en/user-guide/key-pair-auth

Snowflake OAuth / External OAuth (JWT / client credentials)

🔗 https://docs.snowflake.com/en/user-guide/oauth 

 

I’m posting this as a heads-up so the Moveworks team can:

  • Review the current Snowflake plugin and connector authentication options.
  • Update the official Moveworks documentation with the new recommended setup.
  • Provide migration guidance for existing integrations.
  • Ensure new implementations use a future-safe authentication method.

This will help avoid any unexpected outages in Moveworks use cases that depend on Snowflake queries (e.g., fetching customer account details, analytics fetches, etc.).

Hoping this helps the developer community stay ahead of the upcoming Snowflake changes.

Best answer by Kevin Mok

Hey ​@puneegup 

Thanks a ton for sharing this Snowflake announcement!

Good news: this change doesn’t impact our Moveworks → Snowflake integration.

Our connector uses OAuth 2.0 via a Snowflake security integration (custom client) rather than username/password-based auth for a service account. That means:

  • We’re not relying on password auth for non-human/service users
  • Access is handled through OAuth tokens issued by Snowflake
  • We’re already aligned with Snowflake’s move away from passwords and toward stronger, modern auth methods

So from a Moveworks integration/API perspective, there’s nothing customers need to change because of this rollout. We may add a small note in our docs just to reassure folks who see the Snowflake announcement, but the integration itself is already in good shape.

Really appreciate you flagging this!

2 replies

Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • Answer
  • December 1, 2025

Hey ​@puneegup 

Thanks a ton for sharing this Snowflake announcement!

Good news: this change doesn’t impact our Moveworks → Snowflake integration.

Our connector uses OAuth 2.0 via a Snowflake security integration (custom client) rather than username/password-based auth for a service account. That means:

  • We’re not relying on password auth for non-human/service users
  • Access is handled through OAuth tokens issued by Snowflake
  • We’re already aligned with Snowflake’s move away from passwords and toward stronger, modern auth methods

So from a Moveworks integration/API perspective, there’s nothing customers need to change because of this rollout. We may add a small note in our docs just to reassure folks who see the Snowflake announcement, but the integration itself is already in good shape.

Really appreciate you flagging this!


Forum|alt.badge.img+3
  • Author
  • Known Participant
  • December 4, 2025

Hi ​@Kevin Mok - Thank you for your response!

To refresh the token or obtain a code, we currently sign in using a username and password associated with the service account. However, if we need to generate a code to obtain a new refresh token after 90 days without relying on the service account, how can we achieve this?

Kindly advise.

 

https://marketplace.moveworks.com/connectors/snowflake#how-to-implement