Sign in with an OAuth2 provider
Initiate OAuth2 authentication flow with a social provider. Redirects the user to the provider's authorization page. If the user doesn't exist and AUTH_DISABLE_AUTO_SIGNUP is not set, a new account will be created upon callback. When AUTH_DISABLE_AUTO_SIGNUP is enabled, users must use the /signup/provider/{provider} endpoint to register first.
Path parameters
The name of the social provider
Query parameters
Array of allowed roles for the user
[ "me", "user" ]
Default role for the user
Display name for the user
A two or three characters locale
Additional metadata for the user (JSON encoded string)
URI to redirect to
If set, this means that the user is already authenticated and wants to link their account. This needs to be a valid JWT access token.
Opaque state value to be returned by the provider
Additional provider-specific parameters
Extra parameters forwarded to the upstream OAuth2 provider's authorization URL (e.g. Google's prompt or login_hint). Reserved OAuth2/OIDC parameters are rejected.
Extra parameters forwarded to the upstream OAuth2 provider's authorization URL. Reserved OAuth2/OIDC parameters are rejected.
PKCE code challenge (S256). When provided, the callback redirect will contain an authorization code instead of a refresh token.
Response
An error occurred while processing the request
Example response
{
"status": 400,
"message": "Invalid email format"
}