Okta Browser Plugin Fails to Prompt for Password Saving on Dynamic Websites

The Okta Browser Plugin requires static login pages to successfully prompt for and save credentials. Dynamic websites that generate content in real-time and use unique URLs prevent the plugin from auto-populating or saving credentials. The Okta Browser Plugin does not prompt to save passwords when navigating to certain websites.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Browser Plugin
• Secure Web Authentication (SWA)

The target website uses a dynamic login page rather than a static login page. Dynamic sites use client-side JavaScript to generate content in real-time and often generate a unique URL for every interaction. This dynamic generation prevents the Okta Browser Plugin from auto-populating credentials or prompting to save them.

Why does the Okta Browser Plugin fail to prompt on dynamic websites?

A dynamic login page generates content in real-time and allows for a customized experience. Dynamic pages do not pre-render content. A static login page contains pre-rendered pages that a Content Delivery Network (CDN) typically caches and delivers. Static pages remain the same regardless of the browser. Dynamic sites use client-side JavaScript to make pages dynamic in real-time.

On dynamic websites, the served content changes with every interaction. This prevents the Okta Browser Plugin from auto-populating credentials. The Okta Browser Plugin prompts for saving credentials on sites that support Secure Web Authentication (SWA). Static sites maintain SWA compatibility, which allows the prompt to display.

How can a website be identified as dynamic?

Identify a dynamic webpage by interacting with the website URL. A unique URL upon every interaction indicates a dynamic webpage.

Is there currently a solution or workaround for dynamic websites?

Currently, the Okta Browser Plugin does not support automatic credential prompting for dynamic websites. As a workaround, manually add the application to the Okta End-User Dashboard and enter the credentials. Administrators can also configure a custom Secure Web Authentication (SWA) application using specific CSS selectors if the login fields remain consistent. If the service provider supports it, configuring a federated integration, such as SAML or OpenID Connect (OIDC), provides a more robust solution.