.png%3Falt%3Dmedia%26token%3D060e2220-39ef-4b8b-9dce-8688ff38e664)
.png%3Falt%3Dmedia%26token%3D060e2220-39ef-4b8b-9dce-8688ff38e664)
Authentication
An overview of what is the authentication service for your project.
Deskree provides the ability to create user accounts for your back-end using both email/password authentication as well as OAUTH providers.
You can manage your AUTH providers with the Authentication tab of your project. There you will need to input provider-specific attributes to activate each AUTH method. If a provider is missing those attributes for the setup to be complete, it will be indicated by a red exclamation mark sign.
Deskree uses a Bearer token for all requests that require authentication, which must be sent in the Authorization header. The Bearer token is sent as
idToken parameter in a response to user sign-up and sign-in requests in REST APIs and Javascript SDK All requests with permissions set other than
Public require authentication. See Permissions page for more information.- To send a Bearer token when making an API request, you must provide an Authorization header. You can read more in the REST and GraphQL API documentation. Example:headers: { Authorization: `Bearer ${token}` }
To be able to get the token from the sign-up and sign-requests, you must first activate the AUTH provider you are using.
In order to sign-up/sign-in a user using OAUTH providers you need to:
- 1.
- 2.Use the returned
authUrito prompt the user to authenticate with the OAUTH provider - 3.Finally, complete the sign-in process using the returned data either via Javascript SDK or REST AUTH API.
For a practical example visit:
Last modified 8mo ago