Login Session Oauth
Login via OAuth2.0 authorization code flow with PKCE.
The currently supported OAuth2.0 providers are:
- Okta
Request
- The document declares no server URL.
- Auth: none declared
Query parameters
The OAuth provider. At the moment this defaults to 'okta' but this default will be removed in the future. Please specify the provider explicitly to avoid issues.
The name of the account to validate that the user is authorized to access. If the user does not have access to this account, the endpoint will return a 403 even if the user is successfully authenticated. This is useful for third party applications which want users to be restricted to a particular account.
Whether to redirect at the HTTP level or not. Browsers set origin=null if a cross-origin resource redirects to yet another origin. This can be problematic for an embedded iframe. Instead, setting redirect to False puts the redirect information in the response body. Then it is up to the client to handle the redirect themselves.
The URI to redirect to after the login is complete. This is needed for clients to redirect back to the original page. When OAuth is complete, the user will be redirected to this URI. If the login is successful, a session cookie will be set. If the login is unsuccessful, an error parameter will be set in the redirect_uri query params. If this value is set to None then the redirect_uri will default to https://app.numbersstation.ai/login.
Whether to set a third-party cookie for cross-origin iframes.
An optional base64-encoded Slack {team_id}:{user_id} to link to (for use by the NS Slack App).
Response
Successful Response
Changes
No recorded changes to this operation across all 2 revisions of this API.