HTML Quickstart
This guide will only include the frontend integration. If you would like to also handle Session Management in your backend, select your backend technology below:
This is a quickstart guide to help you integrate Descope with your HTML application. Follow the steps below to get started.
Import SDK
You must import our WebJS and Web Component SDKs in order to use the Descope Flows component.
Add Descope SDK and Session Token Logic
To validate whether or not a user is logged in, before deciding to display the login page designed in Flows, use this logic highlighted to the right.
persistTokens
: this will force existing tokens to be included in all outgoing requestsautoRefresh
: this will automatically refresh sessions once they are expired, if the refresh token is valid
Add Flows Component
To trigger the Descope Flow, you will need to add this component. The screens you've customized in your Flow will appear here. You can also customize the component with the following:
flowId
- ID of the flow you wish to useonSuccess
andonError
- functions that execute when authentication succeeds or failstheme
- "light" or "dark", the default is "light"debug
- a boolean that shows a debug widget if true, default is falsetenant
- where you put the<tenant ID>
of the tenant you wish to use in the authentication flowautoRefresh
- a boolean that should be true if you wish to automatically refresh your session tokens across multiple pages,redirectUrl
- Redirect URL for OAuth and SSO (will be used when redirecting back from the OAuth provider / IdP), or for "Magic Link" and "Enchanted Link" (will be used as a link in the message sent to the the user). When configured within the flow, it overrides the configuration within the Descope console.validateOnBlur
- a boolean to configure whether field validation is performed when clicking away from the field (true) or on form submission (false)form
- You can optionally pass flow inputs, such as email addresses, names, etc., from your app's frontend to your flow. The configuredform
inputs can be used within flow screens, actions, and conditionals prefixed withform
.- Ex:
form='{ email: "predefinedname@domain.com", firstName: "test", "customAttribute.test": "aaaa", "myCustomInput": 12 }'
client
- You can optionally pass flow inputs from your app's frontend to your flow. The configured client inputs can be used within flow actions and conditionals prefixed with client..- Ex:
client='{ version: "1.2.0" }'
Handle onSuccess and onError Logic
It's important to make sure that you're handling the onSuccess and onError correctly. You will need to use the descope-wc
document element and if you are using the autoRefresh token feature in the WebJS SDK, you will need to call sdk.refresh()
in onSuccess()
. To extract details on the user, you can load the user details from e.detail.user. On successful authentication, the information about the user is returned and accessible with e.detail.user.
Ex: const onSuccess=(e) => { console.log(e.detail.user.name), console.log(e.detail.user.email)};
Make Sure Session Persists Across All Pages
On all of your frontend pages, you'll need to make sure that sdk.refresh()
is called at the top of each page in <script>
tags. Add the following logic to every authenticated page you have in your application.
Continue with Backend SDK
If you would like to also handle Session Management in your backend, keep on reading by selecting your backend technology below:
Checkpoint
Your application is now integrated with Descope. Please test with sign-up or sign-in use case.
Customize
Now that you have the end-to-end application working, you can choose to configure and personalize many different areas of Descope, including your brand, style, custom user authentication journeys, etc. We recommend starting with customizing your user-facing screens, such as signup and login.