Snowflake supports federated authentication through SAML 2.0 security integrations, allowing users to authenticate through an organization's identity provider rather than managing separate Snowflake passwords.
For manually configured SAML integrations, Snowflake requires information describing how to communicate with and validate responses from the identity provider.
Option B is correct because the IdP's SSO URL identifies the endpoint used during SAML authentication. Snowflake stores this information in the SAML2_SSO_URL integration property.
Option D is correct because Snowflake requires the identity provider's signing certificate to verify the authenticity and integrity of SAML assertions. This is represented by SAML2_X509_CERT.
Option A is insufficiently specific. General identity-provider account details do not replace the required federation configuration values.
Option C is incorrect because the SAML protocol defines the relevant authentication message structure.
Option E is incorrect because Snowflake does not require the identity provider's private encryption key. Private cryptographic keys must remain protected by their owners.
Current-version qualification: Snowflake now recommends supplying an IdP metadata URL for supported providers, including Okta and Microsoft Entra ID. When configured through METADATA_URL, Snowflake obtains the relevant IdP settings automatically rather than requiring administrators to supply the SSO URL and certificate individually.
Thus, B and D remain correct for manual configuration, but the question's use of must is too absolute for current supported methods.
Official Snowflake references: Configuring an Identity Provider for Snowflake; CREATE SECURITY INTEGRATION (SAML2).
Submit