Authentication - Native
A high-level overview of how authentication works with a native mobile or desktop app.
Login
Steps:
- The user clicks the Login button within your native application.
- The native app creates an Authorization Request and sends the user to a browser for redirection to the Wristband Authorize Endpoint.
- Wristband validates and records the Authorization Request and redirects the user to the Wristband-hosted Login page.
- The user provides their credentials to authenticate.
- The Login Page redirects back to the native app's Callback Endpoint with an authorization code via deep linking.
- The Callback Endpoint calls Wristband's Token Endpoint to exchange the authorization code for an access token.
- The Callback Endpoint stores the access token and refresh token in secure storage.
- The user is redirected to your native app's entry point.
Logout
Steps:
- The user clicks the Logout button within your native app.
- The app invokes a
logout()
function, destroying tokens in secure storage. - The app calls the Revoke Token Endpoint to revoke the refresh token.
- The user is redirected to the Wristband Logout Endpoint.
- Wristband destroys the authentication session and redirects the user to your app's Login screen via deep linking.
Updated 7 days ago