Get desktop application:
View/edit binary Protocol Buffers messages
The service to manage public endpoints in Users
Login authenticats a user and returns a access/refresh token
Login request with either user identifier & email or client credentials.
User identifier & password.
Client credentials from service account.
Login response with tokens and user information.
The access token and refresh token.
ID of the user.
User information.
Logout validates the access token and blocks it afterwards
Empty logout request. The user ID etc. is taken from the token.
(message has no fields)
Empty response to the logout request.
(message has no fields)
Get the logged in user
Get request to get the logged in user. The user ID etc. is taken from the token.
(message has no fields)
Response with user information to the get request.
Information about the user.
ID of the user
Register creates a new user
Register request for users to self-register. This is only possible with the register bool set in users settings.
User identifier & password for the new user.
Register response with tokens and user information.
Access and refresh token for the new logged in user.
User ID of the new user.
Information about the new user.
Send reset password email to the user
Request to send a reset password email to the user. This is only possible if an email provider is configured, and the user has an email.
User identifier of the user.
Empty response to the send password reset request
JWT token to reset the password.
Reset password of the user
Request to reset the password of a user with a verification code sent to the email.
The 6 digit verification code
The new password
Identifier of the user
JWT token to reset the password.
Empty response to the reset password request
(message has no fields)
Delete logged in user
Request to delete the logged in user. The user ID etc. is taken from the token.
(message has no fields)
Empty response to the delete request.
(message has no fields)
Refresh logged in token pair
Request to refresh the access and refresh token of the logged in user.
The access token of the user Refresh token matching the access token.
Response with new access and refresh token.
New refresh and access tokens
Get auth config for how available login methods
Empty Request to get the auth config containing the available login mechanisms and if self-registering is enabled.
(message has no fields)
Response with the auth config containing the available login mechanisms and if self-registering is enabled.
The name of the project
The logo of the project
If to validate password
Array of supported login methods.
True if new users can sign up.
SSO login options
Verify email
Request to verify the email of a user with a verification code sent to the email.
The verification code.
The email of the user.
JWT token to verify the email.
Empty response to the Verify Email Request.
(message has no fields)
Verify phone number
Request to verify the phone number of a user with a verification code sent to the phone number.
Empty response to the Verify Phone Number Request.
(message has no fields)
Request to send an email containing the code for the email verification flow. This is an upsert, and will invalidate the current verification-code if it exists. Only possible if an email-provider is configured, and the user has en email.
User identifier of the user.
Empty response for sending a verification email
JWT token to verify the email.
Used in:
ID of the service account
secret of the service account
Represents an SSO provided ID of a user
What type of SSO this ID is from
The ID of the SSO provider
The ID provided by SSO
The internal user ID
A login option for using SSO. This might be merged into GetAuthConfigResponse.login_types, but is introduced as a separate field, to maintain backwards compatibility.
Used in:
Type of SSO. Currently only OIDC is supported.
ID of the SSO provider as given in the platform configuration.
Name of SSO provider. This is an optional human readable version of the provider ID.
URL of the underlying issuer. This can be used in the frontend for showing specific items for certain known issuers.
The type of SSO. Currently only OIDC is supported.
Used in:
,Used in:
, ,Access token
Refresh token
Used in:
,Identifier of user. This can be username, email etc.
Password of the user