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 solution requires administrators to configure custom Secure Web Authentication (SWA) applications or federated integrations.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Browser Plugin
• SWA

The Okta Browser Plugin fails to prompt on dynamic websites due to real-time content generation.

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 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 SWA. Static sites maintain SWA compatibility, which allows the prompt to display.

What indicates a dynamic website?

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

What is the solution 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.

NOTE: End users can only add sites absent from the application catalog via Add a bookmark instead. Bookmarks do not store credentials and only navigate to the URL. The solution to this limitation requires Super Admins to add custom SWA applications or other sign-on methods, such as Security Assertion Markup Language (SAML) or OpenID Connect (OIDC), because Okta limits users to applications already available in the catalog.

Administrators can configure a custom SWA application using specific Cascading Style Sheets (CSS) selectors if the login fields remain consistent. If the service provider supports it, configuring a federated integration, such as SAML or OIDC, provides a more robust solution.