Partner authentication support¶
This topic describes which partner applications support External OAuth, Snowflake OAuth, and key pair authentication.
Interactive authentication support¶
Interactive authentication for human users (that is, users with their TYPE set to PERSON or
NULL) uses an authorization code flow.
The following table describes which applications support External OAuth, Snowflake OAuth, and key pair authentication for human users :
Note
Human and service users cannot access Snowsight using key pair authentication.
Application |
External OAuth |
Snowflake OAuth |
Key pair authentication |
|---|---|---|---|
Yes (Only Microsoft Entra ID is supported) |
No |
No |
|
Yes (Only Microsoft Entra ID is supported) |
No |
No |
|
Yes |
Yes |
Yes |
|
Yes |
Yes |
No |
|
No |
Yes |
Yes |
|
No |
Yes |
Yes |
|
N/A |
N/A |
Yes |
|
Yes |
Yes |
Yes |
|
No |
No |
Yes |
|
No |
No |
Yes |
|
No |
No |
Yes |
|
No |
Yes |
Yes |
|
Yes |
Yes |
Yes |
|
Strategy Cloud (BI) |
Yes |
No |
Yes |
Strategy Workstation/Developer (BI) |
Yes |
No |
No |
Service-to-service authentication support¶
Service-to-service authentication for service users (that is, users with their TYPE set to SERVICE) uses a
client credential flow.
The following table describes which applications support External OAuth and key pair authentication for service users :
Note
Human and service users cannot access Snowsight using key pair authentication.
Application |
External OAuth |
Key pair authentication |
|---|---|---|
No |
No |
|
No |
No |
|
No |
Yes |
|
No |
No |
|
No |
Yes |
|
No |
Yes |
|
Yes |
Yes |
|
No |
Yes |
|
No |
Yes |
|
No |
Yes |
|
No |
Yes |
|
Yes |
Yes |
|
No |
Yes |
|
Strategy Cloud (BI) |
No |
Yes |
Strategy Workstation/Developer (BI) |
No |
No |