Overview
Deskree provides the ability to create user accounts for your back-end using both email/password authentication as well as OAUTH providers.
Last updated
Deskree provides the ability to create user accounts for your back-end using both email/password authentication as well as OAUTH providers.
Last updated
Manage your authentication providers seamlessly via the Authentication tab within your project. Here, you'll need to provide provider-specific attributes to enable each authentication method. By default, the Email/Password option is set up. Within this section, you have the capability to configure authentication providers such as Google, GitHub, and Facebook.
In case you're configuring a provider and essential details are absent, we'll alert you with a red exclamation mark. Additionally, a friendly reminder: ensure to click the deploy button to effectively implement your modifications!
Before signing up or signing in a user using OAUTH providers, it's imperative to activate the AUTH provider you intend to use. Follow these steps:
Access the authentication section by navigating through the sidebar.
Utilize the obtained authUri to prompt the user to authenticate with the chosen OAUTH provider.
Conclude the sign-in process by utilizing the returned data, either through the Javascript SDK or REST AUTH API.
Deskree employs a Bearer token for any authenticated requests, necessitating its inclusion in the Authorization header. This Bearer token, denoted as the idToken parameter, is transmitted as part of the response to user sign-up and sign-in requests in both and the .
Authentication is mandatory for all requests with permissions set to anything other than Public. For additional details, please refer to the page.
To send a Bearer token when making an API request, you must provide an Authorization header. You can find more information in the and documentation.
How to get a Bearer token in Deskree and
Generate an OAUTH sign-in URL using either the or .
