Account Management and Data Governance · Topic 3 of 8
Authentication Methods
Compare Snowflake authentication options: passwords with MFA, federated authentication and SSO through SAML, Snowflake and External OAuth, and key pairs.
- 5 min
- User TYPE: PERSON for humans, SERVICE for non-interactive users with no password, LEGACY_SERVICE being deprecated.
- MFA factors: passkeys, authenticator apps (TOTP) and Duo. Enforce with an authentication policy.
- Federated authentication uses SAML 2.0 with an external IdP; SSO is the result. Configure a SAML2 security integration.
What it is
Authentication proves who is connecting. Authorization, covered by roles, then decides what that identity may do.
Snowflake supports several methods, and the right one depends on who connects. People sign in through Snowsight or tools, while services such as pipelines and applications connect without a person present.
Each user has a TYPE property. PERSON is a human user, SERVICE is a non-interactive user that cannot use a password, and LEGACY_SERVICE is a service user still allowed a password, which Snowflake is deprecating.
How it works
Methods at a glance
| Method | Who it suits | How identity is proven |
|---|---|---|
| Password with MFA | People without an identity provider | Password plus a second factor |
| Federated authentication and SSO | People in a company with an identity provider | A SAML 2.0 assertion from the IdP |
| Snowflake OAuth | Users of partner or custom apps | A token issued by Snowflake |
| External OAuth | Apps using the company's OAuth server | A token issued by Okta, Microsoft Entra ID or another server |
| Key-pair authentication | Services, scripts, connectors | A private key signs a JWT, Snowflake checks the public key |
Service users can also use programmatic access tokens and workload identity federation, but the exam outline focuses on the five methods above.
Multi-Factor Authentication (MFA)
MFA adds a second factor after the password. Snowflake supports passkeys (recommended), authenticator apps that generate time-based one-time passcodes (TOTP), and Duo.
Users enroll themselves in Snowsight. Snowflake is moving to require MFA for every human user who signs in with a password, and newer accounts require enrollment by default.
Administrators enforce MFA with an authentication policy. Its MFA_ENROLLMENT property makes enrollment required, and MFA_POLICY can limit which second factors are allowed.
Tools that open many connections can prompt for MFA repeatedly. Setting ALLOW_CLIENT_MFA_CACHING to TRUE on the account lets supported clients cache an MFA token for up to four hours.
Federated authentication and SSO
In federated authentication, Snowflake trusts an external identity provider (IdP) to authenticate users. Snowflake is the service provider, and the IdP sends a SAML 2.0 assertion that identifies the user.
Single Sign-On (SSO) is what the user experiences: sign in once to the IdP, then reach Snowflake without a separate password. Okta and Microsoft AD FS have native support, and other SAML 2.0 IdPs such as Microsoft Entra ID work too.
Configure it with a SAML2 security integration (CREATE SECURITY INTEGRATION ... TYPE = SAML2). The user must still exist in Snowflake, often created automatically by SCIM provisioning from the IdP.
SSO users are not required to use Snowflake MFA, because the IdP handles the strong sign-in. An authentication policy can still demand Snowflake MFA after the IdP step.
OAuth
OAuth lets an application connect on behalf of a user with a token, so the app never stores the user's password.
| Type | Authorization server | Security integration |
|---|---|---|
| Snowflake OAuth | Snowflake | TYPE = OAUTH |
| External OAuth | Okta, Microsoft Entra ID, PingFederate or a custom server | TYPE = EXTERNAL_OAUTH |
Snowflake OAuth suits partner tools such as Tableau or custom clients. External OAuth suits companies that already issue tokens from their own server.
Key-pair authentication
The user generates an RSA key pair, at least 2048 bits. The public key is set on the user with ALTER USER ... SET RSA_PUBLIC_KEY = '...', and the client keeps the private key, optionally encrypted with a passphrase.
Drivers, the Snowflake CLI, connectors and Snowpipe Streaming clients sign a token with the private key. A second slot, RSA_PUBLIC_KEY_2, allows key rotation without downtime: add the new key, move clients over, then remove the old one.
Authentication policies
An authentication policy controls which methods and clients an account or user may use, with properties such as AUTHENTICATION_METHODS, CLIENT_TYPES and MFA_ENROLLMENT. It can be set on the account or on individual users.
Common mistakes
Calling SSO and federated authentication different features. Federated authentication is the trust between Snowflake and the IdP; SSO is the resulting sign-in experience.
Giving a pipeline a password. Services should use key pairs or OAuth, not passwords. SERVICE users cannot have a password at all.
Picking External OAuth when Snowflake issues tokens. If Snowflake is the authorization server, it is Snowflake OAuth.
Thinking key rotation needs downtime. RSA_PUBLIC_KEY_2 holds the second key during rotation.
What to remember for the exam
- User TYPE: PERSON for humans, SERVICE for non-interactive users with no password, LEGACY_SERVICE being deprecated.
- MFA factors: passkeys, authenticator apps (TOTP) and Duo. Enforce with an authentication policy.
- Federated authentication uses SAML 2.0 with an external IdP; SSO is the result. Configure a SAML2 security integration.
- Snowflake OAuth: Snowflake issues tokens. External OAuth: your own authorization server issues them.
- Key pair: RSA 2048-bit minimum, public key on the user, private key on the client, RSA_PUBLIC_KEY_2 for rotation.
Losing the private key of a service user locks that service out. Store it in a secrets manager and plan rotation with the second key slot.
Check yourself
Which authentication method best suits a nightly ETL job that must not use a password?
Key-pair authentication, with the public key set on a SERVICE user and the private key kept by the job.
A company's Okta tenant must handle all employee sign-ins to Snowflake. What does the administrator configure?
Federated authentication with a SAML2 security integration, which gives users SSO through Okta.
What is the difference between Snowflake OAuth and External OAuth?
In Snowflake OAuth, Snowflake issues the tokens. In External OAuth, an external server such as Okta or Microsoft Entra ID issues them.
Topic 3 of 8 in Account Management and Data Governance
Test yourself on Account Management and Data Governance
The full Snowflake SnowPro Core COF-C03 question bank has 845 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.