Mobile Auth States
How authentication states behave on mobile for each strategy, and what your application is responsible for.
Mobile Flows Only
This section covers authentication states for mobile-initiated flows only. Desktop-initiated flows (QR code scanning) are covered in Desktop Flow. Error codes and handling are covered in Error Handling.
Android Digital Credentials
With TS.43, the user never leaves your application. The only UI added by Glide is the native Android secure prompt (Digital Credentials API), which is an OS-level dialog managed by Android itself.
Loading
Your responsibility. Show a loading indicator while waiting for the credential response.
Success
Your responsibility. The SDK returns the result directly to your app. Display confirmation as needed.
Error
Your responsibility. Handle error codes returned by the SDK and show appropriate messaging or fallbacks.
App Clips & Carrier Apps
Link flows open the carrier's App Clip or native app, which redirects through the user's default browser to the carrier's OAuth server. After verification, the carrier redirects to Glide's callback URL, and Glide then redirects to your application's pre-configured redirect endpoint. This two-step redirect ensures secure session binding across domains.
Redirect Chain
After the carrier authenticates the device, the browser is redirected through two endpoints before reaching its final destination. You provide your redirect URL during integration setup, and you choose how the flow ends for the user.
Glide's Redirect URL
Glide receives the carrier's OAuth callback, processes the verification, and can optionally show a Glide-hosted success or error page at this step.
Your Redirect URL Recommended
Glide redirects to your endpoint under your domain. This is recommended because your endpoint is the only place that can verify the device completing the authentication is the same one that initiated the flow, through your existing session cookies and domain context. From here you can show a branded page, close the tab, or handle it however you need.
Post-Authentication Options
| Option | Glide's Step | Your Step |
|---|---|---|
| Silent close | No UI, redirects immediately | Close the tab on your endpoint |
| Glide-hosted page | Shows success/error page briefly | Receives redirect after |
| Your branded page | No UI, redirects immediately | Show your own success/error page |
Loading
Your responsibility. The SDK waits for a signal that the user completed the carrier flow. Show a loading indicator in your app during this time.
Success
By default, the browser tab closes silently. The SDK resolves with the result in your app. Display confirmation as needed.
Error
By default, the browser tab closes silently. The SDK returns the error in your app. Handle accordingly.
Seamless Carrier Flows (e.g. Verizon on Android)
Some carriers (like Verizon on Android) support a fully seamless verification that requires no consent prompt and no redirect. The entire flow happens in the background with no visible UI to the user. See Consent Overview for details.
No consent prompt is shown to the user
No browser tab or external app is opened
No redirect URI is used
Loading and result states are still your responsibility to display in your app
Summary
| Strategy | User Leaves App? | Glide UI Shown? | State Management |
|---|---|---|---|
| TS.43 | No | OS consent prompt only | Fully your responsibility |
| Link (App Clips / Carrier Apps) | Briefly | Redirects to your endpoint | Your redirect endpoint + your app |
| Headless (e.g. Verizon) | No | None | Fully your responsibility |