feat(ingest/snowflake): Okta OAuth support; update docs #8157
Conversation
github-actions
bot
added
the
ingestion
| + Ensure client authentication method is `Client secret` | ||
| - Create an Okta user to sign into, noting the `Username` and `Password` | ||
| - Create a Snowflake user to correspond to your newly created Okta client credentials | ||
| + *Ensure the user's `Login Name` matches your Okta user's `Username` (likely a password)* |
There was a problem hiding this comment.
What does this mean -
likely a password?
There was a problem hiding this comment.
Oops, supposed to be email, thx
| raise ValueError( | ||
| f"'oauth_config.scopes' was none " | ||
| f"but should be set when using {v} authentication" | ||
| "Certificate authentication is not supported for Okta." |
There was a problem hiding this comment.
If this is always true for okta, it would help to move this to a validator in OAuthConfiguration .
There was a problem hiding this comment.
Pretty sure you can set up okta auth with public / private keys, I just couldn't get it to work easily with snowflake
| logger.info(f"using authenticator type '{v}'") | ||
| return v | ||
| elif oauth_config.client_secret is None: | ||
| raise ValueError( |
There was a problem hiding this comment.
can some of this validation logic live on the OAuthConfiguration object?
There was a problem hiding this comment.
Probably, but I'm not sure what will be snowflake specific and what won't just yet.
There was a problem hiding this comment.
thanks for updating these docs
OauthConfiguration, to simplify logicOPERATEpermissionChecklist