What you will be able to do
- Decide which users Snowflake MFA applies to, and enforce it with an authentication policy, including for SSO users
- Restrict which authenticators users may enroll and explain why passkeys are preferred
- Recover a locked-out user and provision break-glass access with one-time passcodes
- Configure a SAML2 security integration and diagnose the common causes of failed SSO sign-ins
Key concept
Authentication policy — An authentication policy is a Snowflake object that you set on the account or on a user. It decides which sign-in methods are allowed, whether MFA enrollment is required, which second factors count, and how programmatic access tokens behave. Most hardening in this subdomain comes down to writing one of these policies and attaching it at the right level.
1.Who Snowflake MFA applies to, and how a policy enforces it
Snowflake MFA protects one kind of sign-in: a human user who enters a password. After the password, that user has to present a second factor. Service users are outside this scheme altogether. A pipeline account cannot respond to a passkey prompt, so service users authenticate another way, such as a key pair or a token.
The default depends on when the account was created. In accounts created after the 2024_08 behavior change bundle was enabled, every human password user must enroll in MFA unless you do something about it. Older accounts have to be configured before MFA becomes mandatory. A newer account can relax the requirement by setting an authentication policy with MFA_ENROLLMENT=OPTIONAL on the account. Even then, password users who sign in to Snowsight still need MFA. The relaxation only covers other interfaces, and it is temporary, because Snowflake is phasing out single-factor password sign-ins.
For SSO users, Snowflake trusts the identity provider to enforce MFA or some other strong method. If you also want a Snowflake factor after the IdP step, for example on administrators, you need an authentication policy for it. The policy below allows password, SAML and OIDC sign-ins, requires MFA enrollment, and uses ENFORCE_MFA_ON_EXTERNAL_AUTHENTICATION='ALL' to apply Snowflake MFA to externally authenticated sign-ins too.
CREATE AUTHENTICATION POLICY ACCOUNTADMIN_DOUBLE_MFA
AUTHENTICATION_METHODS = ('PASSWORD', 'SAML', 'OIDC')
SECURITY_INTEGRATIONS = ('<SAML OR OIDC SECURITY INTEGRATIONS>')
MFA_ENROLLMENT = 'REQUIRED'
MFA_POLICY=(ENFORCE_MFA_ON_EXTERNAL_AUTHENTICATION='ALL');Creating a policy enforces nothing; it takes effect only once it is attached. To cover everyone, run ALTER ACCOUNT SET AUTHENTICATION POLICY <policy_name>. To cover one person, run ALTER USER <user_name> SET AUTHENTICATION POLICY <policy_name>. On the account, the optional FOR ALL PERSON USERS or FOR ALL SERVICE USERS clause narrows the policy to one user type, which suits an MFA policy that service users cannot satisfy anyway.
When both levels have a policy, the one set on the user wins over the account's. That makes the pattern in the example above practical: keep a baseline policy on the account and attach a stricter one, such as the double-MFA policy, to administrator users only.
Checkpoint 1 of 6· Fill the gap
Your administrators sign in through a SAML IdP. You also want Snowflake to ask them for its own MFA factor after the IdP sign-in. Which parameter completes this policy?
CREATE AUTHENTICATION POLICY ACCOUNTADMIN_DOUBLE_MFA
AUTHENTICATION_METHODS = ('PASSWORD', 'SAML', 'OIDC')
SECURITY_INTEGRATIONS = ('<SAML OR OIDC SECURITY INTEGRATIONS>')
MFA_ENROLLMENT = 'REQUIRED'
MFA_POLICY=( ? ='ALL');By default, Snowflake leaves strong authentication for SSO users to the IdP. Setting ENFORCE_MFA_ON_EXTERNAL_AUTHENTICATION='ALL' inside MFA_POLICY adds Snowflake MFA after externally authenticated sign-ins. MFA_ENROLLMENT='REQUIRED' alone does not do this for SSO users.
Source: docs.snowflake.comCheckpoint 2 of 6· Check yourself
Your account was created after the 2024_08 bundle was enabled. To relax mandatory MFA, you set an authentication policy with MFA_ENROLLMENT=OPTIONAL on the account. What happens to human password users?
The OPTIONAL setting relaxes MFA only for interfaces other than Snowsight. Password users who sign in to Snowsight must still use MFA, and the opt-out is only temporary.
“Password users who use Snowsight must still use MFA, but MFA isn’t required for other interfaces.”Source: docs.snowflake.com
2.Authenticators, passkeys and restricting the allowed methods
Users choose their second factor from three methods, and an administrator can narrow that list. A passkey is built on the WebAuthn standard. The private key stays somewhere personal to the user: their machine, a hardware key such as a YubiKey, or a password manager. An authenticator app, such as Google Authenticator, Microsoft Authenticator or Authy, generates a time-based one-time passcode (TOTP). Duo is the third option, and your firewall has to be configured before it works. Users add a method in Snowsight under Settings » Authentication. If MFA is required, they are prompted to add one at their next Snowsight sign-in.
| Method | ALLOWED_METHODS value | Administrator consideration |
|---|---|---|
| Passkey (WebAuthn, hardware key, biometrics, password manager) | PASSKEY | Recommended for both security and usability |
| Authenticator app generating a TOTP | TOTP | Included in the CREDENTIALS view |
| Duo | (omit it to prohibit Duo) | Not replicated like the other methods, missing from the CREDENTIALS view, and needs firewall configuration |
To restrict the methods, set MFA_POLICY = (ALLOWED_METHODS = ...) in an authentication policy. The policy below allows passkeys and TOTP but not Duo. Users who already enrolled a method that is now prohibited are not locked out. At their next sign-in they authenticate once with the old method and are then made to enroll an allowed one. That means you can tighten the list without planning a cutover.
CREATE AUTHENTICATION POLICY mfa_policy
MFA_ENROLLMENT = REQUIRED
MFA_POLICY = (ALLOWED_METHODS = ('PASSKEY', 'TOTP'));To audit enrollment, users run SHOW MFA METHODS for their own methods, and administrators run it for another user. For an account-wide view of passkeys and TOTPs, query the CREDENTIALS view. Duo enrollments do not appear there, so a report based only on that view will undercount Duo users.
Checkpoint 3 of 6· Check yourself
A security team updates the account's authentication policy to MFA_POLICY = (ALLOWED_METHODS = ('PASSKEY', 'TOTP')). Several users have only Duo enrolled. What happens the next time one of them signs in?
Restricting ALLOWED_METHODS does not lock out users who enrolled a method that is now prohibited. They use the old method one last time and must then enroll an allowed one. This lets you tighten the list without a planned cutover.
“the next time they sign in they’ll be prompted to authenticate using the pre-existing method, then prompted to configure a new, allowed method.”Source: docs.snowflake.com
3.Recovering locked-out users and break-glass access
When a password user loses their second factor, for example by losing the YubiKey that holds their passkey, an administrator can recover them in one of two ways. The lasting fix is ALTER USER joe ENROLL MFA. If the user has a verified email, Snowflake emails them a prompt to add a new method. If they don't, the statement returns a URL that the administrator passes on to the user. The quick fix is ALTER USER joe SET MINS_TO_BYPASS_MFA = 30, which lets the user sign in with only a password for that many minutes.
Removing a method is a two-step job. Run SHOW MFA METHODS FOR USER joe and copy the value from the name column, for example TOTP-48A7. Then pass that name to ALTER USER joe REMOVE MFA METHOD TOTP-48A7.
Break-glass access solves a different problem: the normal sign-in route is down, for instance because the IdP has an outage. Create a dedicated user, store its password in a key vault, and generate one-time passcodes to keep next to it with ALTER USER breakglass_user ADD MFA METHOD OTP COUNT = 5. An OTP satisfies Snowflake's MFA requirement and is invalidated as soon as it is used. If you run the ADD command again, a new set is generated and every previous OTP is invalidated. Keep a backup MFA method on this user. Once the last OTP is used, the user can be locked out when their session expires.
Checkpoint 4 of 6· Match them up
Match each ALTER USER statement to the situation it is meant for.
Tap a term, then the definition that fits it.
ENROLL MFA is the lasting fix for a lost factor. MINS_TO_BYPASS_MFA only opens a temporary single-factor window. OTPs stored in a vault with a dedicated user's password give break-glass access when normal sign-in is down. REMOVE MFA METHOD retires one named method.
“can help them recover the ability to sign in by temporarily disabling MFA or by helping the user set up a new MFA method”Source: docs.snowflake.com
Sources1
4.Configuring SAML2 SSO and troubleshooting failed sign-ins
Snowflake connects to a SAML identity provider through a SAML2 security integration, created with CREATE SECURITY INTEGRATION ... TYPE = saml2. The integration replaces the deprecated SAML_IDENTITY_PROVIDER account parameter. That parameter still works, but existing setups should migrate to an integration. Snowflake does not configure the IdP side for you.
CREATE SECURITY INTEGRATION my_idp
TYPE = saml2
ENABLED = true
METADATA_URL = 'https://integrator-26580.okta.com/app/ex2kbcS30N697/sso/saml/metadata'
SAML2_SNOWFLAKE_ISSUER_URL = 'https://<orgname>-<account_name>.privatelink.snowflakecomputing.com'
SAML2_SNOWFLAKE_ACS_URL = 'https://<orgname>-<account_name>.privatelink.snowflakecomputing.com/fed/login';METADATA_URL is the preferred way to describe the IdP. With it, Snowflake fetches the IdP's settings, including its certificate, from the IdP itself. If the IdP rotates its signing certificate, run ALTER SECURITY INTEGRATION my_idp REFRESH METADATA_URL to load the new settings without editing any parameter. When every SAML sign-in starts failing right after an IdP certificate change, and the integration itself was not touched, try this refresh first.
The second common failure is a URL mismatch. A Snowflake account can be reached at more than one URL: the legacy URL that the integration falls back to, an account-name URL of the form <orgname>-<account_name>.snowflakecomputing.com, and a privatelink URL (the account-name URL with .privatelink added) for private connectivity. When you set up the IdP, you gave it one of these. The integration's SAML2_SNOWFLAKE_ISSUER_URL is the URL Snowflake presents as its own address, and SAML2_SNOWFLAKE_ACS_URL is the address where the IdP delivers the SAML assertion after the user signs in. The ACS URL is the same base with /fed/login appended. Both must match the URL the IdP holds. If you leave those properties unset, they default to the legacy URL, so an IdP configured with the account-name or privatelink URL will reject the exchange.
The third common failure is identity matching. Unless you set SAML2_REQUESTED_NAMEID_FORMAT, Snowflake requests the emailAddress NameID format, so the IdP has to send the user identifier in the format Snowflake asked for.
After the integration exists, you choose where sign-in starts and how much to harden it. IdP-initiated SSO, for example from an internal portal, needs no Snowflake configuration. SAML2_ENABLE_SP_INITIATED = true turns on Snowflake-initiated sign-in, and SAML2_SP_INITIATED_LOGIN_PAGE_LABEL sets the IdP button text on the Snowflake login page. To encrypt assertions, give the IdP the public certificate in SAML2_SNOWFLAKE_X509_CERT, which you read with DESC SECURITY INTEGRATION. Snowflake decrypts the assertions with a private key it never exports. If your organization requires a CA-issued certificate, generate a CSR with SYSTEM$GENERATE_SAML_CSR. Setting SAML2_SIGN_REQUEST = true makes Snowflake sign its SAML requests, so the IdP can confirm the request did not come from an impersonator.
Checkpoint 5 of 6· Fill the gap
You want Snowflake to pick up an IdP certificate rotation with one REFRESH command, without editing any parameter on the integration. Which parameter completes this integration?
CREATE SECURITY INTEGRATION my_idp
TYPE = saml2
ENABLED = true
? = 'https://integrator-26580.okta.com/app/ex2kbcS30N697/sso/saml/metadata'
SAML2_SNOWFLAKE_ISSUER_URL = 'https://<orgname>-<account_name>.privatelink.snowflakecomputing.com'
SAML2_SNOWFLAKE_ACS_URL = 'https://<orgname>-<account_name>.privatelink.snowflakecomputing.com/fed/login';With METADATA_URL, Snowflake gets the IdP's settings, including its certificate, from the IdP itself. After a rotation, ALTER SECURITY INTEGRATION ... REFRESH METADATA_URL loads the new certificate without changing any parameter. SAML2_SNOWFLAKE_X509_CERT is a different thing: it holds Snowflake's own certificate, which the IdP uses to encrypt assertions.
Source: docs.snowflake.comCheckpoint 6 of 6· Match them up
Each SAML2 problem or requirement below is solved by one integration property. Match them.
Tap a term, then the definition that fits it.
Unset issuer and ACS URLs default to the account's legacy URL, which breaks an IdP set up with a different URL format. Unless SAML2_REQUESTED_NAMEID_FORMAT is set, Snowflake requests emailAddress. SAML2_ENABLE_SP_INITIATED turns on sign-in that starts at Snowflake. SAML2_SIGN_REQUEST makes Snowflake sign its requests so the IdP can verify them.
“If you do not define these properties when creating the security integration, then they default to the legacy URL of the account.”Source: docs.snowflake.com
Sources4
Sources
(4)
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.
“MFA is intended for human users who authenticate with a password. Service users must use another form of authentication.”
↩︎ Who Snowflake MFA applies to, and how a policy enforces it“all human users who authenticate with a password must enroll in MFA by default”
↩︎ Who Snowflake MFA applies to, and how a policy enforces it“Duo is not replicated like the other MFA methods.”
↩︎ Authenticators, passkeys and restricting the allowed methods“temporarily disabling MFA or by helping the user set up a new MFA method”
↩︎ Recovering locked-out users and break-glass access“Using OTPs creates an additional layer of protection and satisfies Snowflake multi-factor authentication requirements.”
↩︎ Recovering locked-out users and break-glass access“As an administrator, you can use an authentication policy to control which MFA methods can be used as a second factor of authentication.”
↩︎ Key concept“Snowflake relies on the identity provider (IdP) to enforce MFA or some other strong authentication method.”
↩︎ Exam trap 1“By default, Snowflake doesn’t require MFA for users who authenticate with single sign-on (SSO).”
↩︎ Prediction“Password users who use Snowsight must still use MFA, but MFA isn’t required for other interfaces.”
↩︎ Checkpoint“the next time they sign in they’ll be prompted to authenticate using the pre-existing method, then prompted to configure a new, allowed method.”
↩︎ Checkpoint“can help them recover the ability to sign in by temporarily disabling MFA or by helping the user set up a new MFA method”
↩︎ Checkpoint - 2.
“Specifies the authentication policy or session policy for the account.”
↩︎ Who Snowflake MFA applies to, and how a policy enforces it“If you explicitly set a policy on a specific user or a specific user type, then that policy takes precedence”
↩︎ Who Snowflake MFA applies to, and how a policy enforces it - 3.
“A passkey is a form of authentication based on the WebAuthn standard, which uses public/private key cryptography.”
↩︎ Authenticators, passkeys and restricting the allowed methods“Note that this view does not include information about Duo authenticators (Duo push and passcodes).”
↩︎ Authenticators, passkeys and restricting the allowed methods - 4.
“The format of this URL must match the URLs in the SAML2_SNOWFLAKE_ISSUER_URL and SAML2_SNOWFLAKE_ACS_URL properties of the security integration.”
↩︎ Configuring SAML2 SSO and troubleshooting failed sign-ins“Note that /fed/login is appended to the URL for the SAML2_SNOWFLAKE_ACS_URL property.”
↩︎ Configuring SAML2 SSO and troubleshooting failed sign-ins“An IdP-initiated SSO does not require configuration in Snowflake.”
↩︎ Configuring SAML2 SSO and troubleshooting failed sign-ins“If the SAML NameID format is not specified, Snowflake uses the following value:”
↩︎ Configuring SAML2 SSO and troubleshooting failed sign-ins“This simplifies the rotation of certificates.”
↩︎ Exam trap 2“If you do not define these properties when creating the security integration, then they default to the legacy URL of the account.”
↩︎ Checkpoint