Admins have been inquiring about the functionality of Okta FastPass in "in-app" browser login flows. Some users have encountered challenges when utilizing it in this specific context and are seeking clarification on its optimal use and any limitations that may exist. To replicate this scenario, a user would attempt to employ Okta FastPass within an application’s built-in browser, observe the process, and note any error messages or issues that arise.
- Okta FastPass
- Usage with WebView2 browsers
- Okta Identity Engine (OIE)
The challenges experienced may stem from the fact that while Okta FastPass does function in “in-app” browser login flows, it is optimized for browser redirection. This is especially true when using standards-based SAML/OIDC flows, which are designed to trigger the FastPass authentication flow most effectively.
- Ensure WebView2 Browser Usage: Verify that the in-app browser being used is a WebView2 browser, as this is a requisite for Okta FastPass to function correctly in such scenarios.
- Implement Browser Redirection: Opt for browser redirection as the primary method to initiate the FastPass authentication flow, especially when using standards-based Security Assertion Markup Language (SAML) / OpenID Connect (OIDC) flows.
