snowflake
Oauth Callback
Changed onComplete the authorization code flow and persist the user's grant.
Not authentication-gated — the browser arrives from Snowflake cross-site and may carry no cookie, so the acting user comes from the single-use transaction handle, redeemed before any other parameter is trusted. A cookie that does arrive must agree with it, or one member could start a flow and lure another into completing it onto the starter's grant, filing the colleague's Snowflake identity under the starter's account.
get/api/snowflake/oauth/callback
Request
- Base URLhttps://api.quadrillion.io (the document declares no server; this is the origin it was published from)
- URLhttps://api.quadrillion.io/api/snowflake/oauth/callback
- Authnone declared
Query parameters
statestring
codestring nullable
errorstring nullable
error_descriptionstring nullable
Response
Successful Response
unknown required
Changes
- info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status
- info
- info
endpoint added
- info