# Configure Microsoft Azure AD for External OAuth¶

This topic describes how to configure Snowflake as an OAuth Resource and Azure AD as an External OAuth Authorization Server to facilitate secure, programmatic access to Snowflake data.

In this Topic:

## Configuration Procedure¶

The following four steps assume that your environment does not have anything configured relating to Azure AD OAuth authorization servers, OAuth clients, scopes, and necessary metadata.

The information from Steps 1-3 will be used to create a security integration in Snowflake.

If you already have an Azure AD authorization server and client configured, it is not necessary to complete all of the steps below. Rather, skim the following three steps and verify that you can obtain the desired information, create scopes, assign scopes to one or more policies, and access the metadata.

If you do not have an Azure AD OAuth authorization server and client configured, complete all of the following four steps.

Important

These steps in this topic are a representative example on how to configure Azure AD for External OAuth.

You can configure Azure AD to any desired state and use any desired OAuth flow provided that you can obtain the necessary information for the security integration (in this topic).

Note that the following steps serve as a guide to obtain the necessary information to create the security integration in Snowflake.

Steps 1-3 are derived from the Azure AD documentation on OAuth 2.0 and Authentication. For more information on how Microsoft defines its terms, its user interface, and options relating to OAuth 2.0 and Authentication consult the following Azure AD guides:

### Prerequisite Step: Determine the OAuth Flow in Azure AD¶

Azure AD supports two different OAuth flows in which an OAuth Client can get an access token.

1. The authorization server can grant the OAuth client an access token on behalf of the user.

2. The authorization server can grant the OAuth client an access token for the OAuth client itself.

In the first flow, the identity in the access token references the user. In the second flow, the identity in the access token references the OAuth client.

Microsoft Azure AD does not allow the same role format for each of these two OAuth flows. The role format to use depends on the OAuth flow in use. After determining which OAuth flow to use:

### Step 1: Configure the OAuth Resource in Azure AD¶

1. Navigate to the Microsoft Azure Portal and authenticate.

2. Navigate to Azure Active Directory.

3. Click on App Registrations.

4. Click on New Registration.

5. Enter Snowflake OAuth Resource, or similar value as the Name.

6. Verify the Supported account types is set to Single Tenant.

7. Click Register.

8. Click on Expose an API.

9. Click on the Set link next to Application ID URI to set the Application ID URI.

Important

The Application ID URI must be unique within your organization’s directory, such as https://your.company.com/4d2a8c2b-a5f4-4b86-93ca-294185f45f2e. This value will be referred to as the <SNOWFLAKE_APPLICATION_ID_URI> in the subsequent configuration steps.

If the Application ID URI is not used, then it is necessary to create a security integration with audiences using the Snowflake Account URL (i.e. <account_identifier>.snowflakecomputing.com). For more information, see:

10. To add a Snowflake Role as an OAuth scope for OAuth flows where the programmatic client acts on behalf of a user, click on Add a scope to add a scope representing the Snowflake role.

• Enter the scope by having the name of the Snowflake role with the session:scope: prefix. For example, for the Snowflake Analyst role, enter session:scope:analyst.

• Select who can consent.

• Enter a display name for the scope (e.g.: Account Admin).

• Enter a description for the scope (e.g.: Can administer the Snowflake account).

• Click Add Scope.

11. To add a Snowflake Role as a Role for OAuth flows where the programmatic client requests an access token for itself:

• Click on Manifest.

• Locate the appRoles element.

• Enter an App Role with the following settings.

Setting

Description

allowedMemberTypes

Application.

description

A description of the role.

displayName

A friendly name for users to view.

id

A unique ID. You can use the [System.Guid]::NewGuid() function from PowerShell to generate a unique ID if needed.

isEnabled

Set to true.

lang

The language. Set to null.

origin

Set to Application.

value

Set to the name of the Snowflake role with the session:role: prefix. . For the Analyst role, enter session:role:analyst.

The App Role manifests as follows.

"appRoles":[
{
"allowedMemberTypes": [ "Application" ],
"isEnabled": true,
"lang": null,
"origin": "Application",
"value": "session:role:analyst"
}
]

12. Click Save.

### Step 2: Create an OAuth Client in Azure AD¶

1. Navigate to the Microsoft Azure Portal and authenticate.

2. Navigate to Azure Active Directory.

3. Click on App Registrations.

4. Click on New Registration.

5. Enter a name for the client such as Snowflake OAuth Client.

6. Verify the Supported account types is set to Single Tenant.

7. Click Register.

8. In the Overview section, copy the ClientID from the Application (client) ID field. This will be known as the <OAUTH_CLIENT_ID> in the following steps.

9. Click on Certificates & secrets and then New client secret.

10. Add a description of the secret.

11. Select never expire. For testing purposes, select secrets that never expire.

12. Click Add. Copy the secret. This will be known as the <OAUTH_CLIENT_SECRET> in the following steps.

13. For programmatic clients that will request an Access Token on behalf of a user, configure Delegated permissions for Applications as follows.

• Click on API Permissions.

• Click on Add Permission.

• Click on My APIs.

• Click on the Snowflake OAuth Resource that you created in Step 1: Configure the OAuth Resource in Azure AD.

• Click on the Delegated Permissions box.

• Check on the Permission related to the Scopes defined in the Application that you wish to grant to this client.

• Click Add Permissions.

• Click on the Grant Admin Consent button to grant the permissions to the client. Note that for testing purposes, permissions are configured this way. However, in a production environment, granting permissions in this manner is not advisable.

• Click Yes.

14. For programmatic clients that will request an Access Token for themselves, configure API permissions for Applications as follows.

• Click on API Permissions.

• Click on Add Permission.

• Click on My APIs.

• Click on the Snowflake OAuth Resource that you created in Step 1: Configure the OAuth Resource in Azure AD.

• Click on the Application Permissions.

• Check on the Permission related to the Roles manually defined in the Manifest of the Application that you wish to grant to this client.

• Click Add Permissions.

• Click on the Grant Admin Consent button to grant the permissions to the client.Note that for testing purposes, permissions are configured this way. However, in a production environment, granting permissions in this manner is not advisable.

• Click Yes.

### Step 3: Collect Azure AD Information for Snowflake¶

1. Navigate to the Microsoft Azure Portal and authenticate.

2. Navigate to Azure Active Directory.

3. Click on App Registrations.

4. Click on the Snowflake OAuth Resource that you created in Step 1: Configure the OAuth Resource in Azure AD.

5. Click on Endpoints in the Overview interface.

6. On the right-hand side, copy the OAuth 2.0 token endpoint (v2) and note the URLs for OpenID Connect metadata and Federation Connect metadata.

• The OAuth 2.0 token endpoint (v2) will be known as the <AZURE_AD_OAUTH_TOKEN_ENDPOINT> in the following configuration steps. The endpoint should be similar to https://login.microsoftonline.com/90288a9b-97df-4c6d-b025-95713f21cef9/oauth2/v2.0/token.

• For the OpenID Connect metadata, open in a new browser window.

• Locate the "jwks_uri" parameter and copy its value.

• This parameter value will be known as the <AZURE_AD_JWS_KEY_ENDPOINT> in the following configuration steps. The endpoint should be similar to https://login.microsoftonline.com/90288a9b-97df-4c6d-b025-95713f21cef9/discovery/v2.0/keys.

• For the Federation metadata document, open the URL in a new browser window.

• Locate the "entityID" parameter in the XML Root Element and copy its value.

• This parameter value will be known as the <AZURE_AD_ISSUER> in the following configuration steps. The entityID value should be similar to https://sts.windows.net/90288a9b-97df-4c6d-b025-95713f21cef9/.

### Step 4: Create a Security Integration in Snowflake¶

This step involves creating a security integration in Snowflake to ensure that Snowflake can communicate with Microsoft Azure AD securely, validate the tokens from Azure AD, and provide the appropriate Snowflake data access to users based on the user role associated with the OAuth token.

Choose the security integration that best addresses your use case and configuration needs. If your integration is only based on the preceding configuration, use the first security integration. For more information, see CREATE SECURITY INTEGRATION.

Important

If you are trying to create a security integration for Microsoft Power BI, follow the setup instructions in Power BI SSO to Snowflake.

Only account administrators (i.e. users with the ACCOUNTADMIN role) or a role with the global CREATE INTEGRATION privilege can execute this SQL command.

The security integration parameter values are case-sensitive, and the values you put into the security integration must match those values in your environment. If the case does not match, it is possible that the access token will not be validated, resulting in a failed authentication attempt.

Verify all values are an exact match. For example, if the Issuer value does not end with a backslash and the security integration is created with a backslash character at the end of the URL, an error message will occur. It would then be necessary to drop the security integration object using DROP INTEGRATION and then create the object again with the correct Issuer value using CREATE SECURITY INTEGRATION.

Create a Security Integration for Azure AD

create security integration external_oauth_azure_1
type = external_oauth
enabled = true
external_oauth_type = azure
external_oauth_token_user_mapping_claim = 'upn'


Create a Security Integration with Audiences

The external_oauth_audience_list parameter of the security integration must match the Application ID URI that you specified while configuring Azure AD.

create security integration external_oauth_azure_2
type = external_oauth
enabled = true
external_oauth_type = azure
external_oauth_audience_list = ('<SNOWFLAKE_APPLICATION_ID_URI>')
external_oauth_token_user_mapping_claim = 'upn'


### Modifying Your External OAuth Security Integration¶

You can update your External OAuth security integration by executing an ALTER statement on the security integration.

For more information, see ALTER SECURITY INTEGRATION (External OAuth).

### Using ANY Role with External OAuth¶

In the configuration step to create a security integration in Snowflake, the OAuth access token includes the scope definition. Therefore, at runtime, using the External OAuth security integration allows neither the OAuth client nor the user to use an undefined role in the OAuth access token.

After validating the access token and creating a session, the ANY role can allow the OAuth client and user to decide its role. If necessary, the client or the user can switch to a role that is different that the role defined in the OAuth access token.

To configure ANY role, define the scope as SESSION:ROLE-ANY and configure the security integration with the external_oauth_any_role_mode parameter. This parameter can have three possible string values:

• DISABLE does not allow the OAuth client or user to switch roles (i.e. use role <role>;). Default.

• ENABLE allows the OAuth client or user to switch roles.

• ENABLE_FOR_PRIVILEGE allows the OAuth client or user to switch roles only for a client or user with the USE_ANY_ROLE privilege. This privilege can be granted and revoked to one or more roles available to the user. For example:

grant USE_ANY_ROLE on integration external_oauth_1 to role1;

revoke USE_ANY_ROLE on integration external_oauth_1 from role1;


Define the security integration as follows:

create security integration external_oauth_1
type = external_oauth
enabled = true
external_oauth_any_role_mode = 'ENABLE'
...


### Using Secondary Roles with External OAuth¶

The desired scope for the primary role is passed in the external token: either the default role for the user (session:role-any) or a specific role that was granted to the user (session:role:<role_name>).

By default, Snowflake does not activate the default secondary roles for a user (i.e. the DEFAULT_SECONDARY_ROLES) user in the session.

To activate the default secondary roles for a user in a session and allow executing the USE SECONDARY ROLES command while using External OAuth, complete the following steps:

1. Configure the security integration for the connection. Set the EXTERNAL_OAUTH_ANY_ROLE_MODE parameter value to either ENABLE or ENABLE_FOR_PRIVILEGE when you create the security integration (using CREATE SECURITY INTEGRATION) or later (using ALTER SECURITY INTEGRATION).

2. Configure the authorization server to pass the static value of session:role-any in the scope attribute of the token. For more information about the scope parameter, see External OAuth Overview.

### Using Client Redirect with External OAuth¶

Snowflake supports using Client Redirect with External OAuth, including using Client Redirect and OAuth with supported Snowflake Clients.

For more information, see Redirecting Client Connections.

### Using Network Policies with External OAuth¶

Currently, network policies cannot be added to your External OAuth security integration. However, you can still implement network policies that apply broadly to the entire Snowflake account.

If your use case requires a network policy that is specific to the OAuth security integration, use Snowflake OAuth. This approach allows the Snowflake OAuth network policy to be distinct from other network policies that may apply to the Snowflake account.

For more information, see OAuth and Network Policies.

### Using Replication with External OAuth¶

Snowflake supports replication and failover/failback of the External OAuth security integration from a source account to a target account.

## Testing Procedure¶

In the context of testing OAuth while using Azure AD as an authorization server, you must:

1. Verify that the test user exists in Azure AD and has a password.

2. Verify that the test user exists in Snowflake with their login_name attribute value set to the <AZURE_AD_USER_USERNAME>

3. Grant the SYSADMIN role to this user.

4. Register an OAuth Client.

5. Allow the OAuth Client to make a POST request to the Azure AD Token endpoint as follows:

• Grant type set to Resource Owner

• HTTP Basic Authorization header containing the clientID and secret

• FORM data containing the user’s username & password

• Include scopes

Here is an example for getting an access token using cURL. Note that the scope must be fully qualified, including the Azure App URI (e.g. scope=https://example.com/wergheroifvj25/session:role-any).

curl -X POST -H "Content-Type: application/x-www-form-urlencoded;charset=UTF-8" \
--data-urlencode "client_id=<OAUTH_CLIENT_ID>" \
--data-urlencode "client_secret=<OAUTH_CLIENT_SECRET>" \
--data-urlencode "scope=<AZURE_APP_URI+AZURE_APP_SCOPE>" \


## Connecting to Snowflake with External OAuth¶

After configuring your security integration and obtaining your access token, you can connect to Snowflake using one of the following:

Note the following:

• It is necessary to set the authenticator parameter to oauth and the token parameter to the external_oauth_access_token.

• When passing the token value as a URL query parameter, it is necessary to URL-encode the token value.

• When passing the token value to a Properties object (e.g. JDBC Driver), no modifications are necessary.

For example, if using the Python Connector, set the connection string as shown below.

ctx = snowflake.connector.connect(