<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
SWA App Does Not Autofill Credentials
Administration
Okta Classic Engine
Okta Identity Engine
Overview
A new or already existing Secure Web Authentication (SWA) app does not auto-populate the user's credentials.
Applies To
  • Secure Web Authentication (SWA)
  • Template App Plugin
Solution
  1. Clean the cache and cookies from the browser.
  2. Reinstall the Okta plugin.
  3. If this is a custom SWA application, check the configuration (the URL and the CSS selectors) again.
  4. Access the SWA application again.

In addition to the above, please check if the tenant has both of the following authentication policies:

  • An authentication policy that allows the Template Plugin App to authenticate with only 1FA.
  • An authentication policy that requires multi-factor authentication for the Okta Browser Plugin.

If the configuration matches this condition, please modify one to align with the other.

 

If the login flow is still failing, this can be expected, depending on the type of login page being served.

  • A dynamic login page generates its content in real time and allows for a more customized experience for the end user. In doing so, the content is not pre-rendered. On the other hand, a static login page contains pre-rendered pages that are typically cached and delivered via a Content Delivery Network (CDN). Static pages remain the same for all users regardless of the browser. Dynamic sites use client-side JavaScript to make pages dynamic in real time.
  • If a website is dynamic, the content that is served will change with every interaction, which prevents the plugin from being able to select the fields and auto-populate credentials.
  • The Okta browser plugin will prompt for saving the credentials on sites that support SWA. If the site is static, it will be SWA compatible, which will allow for the prompt to show. When interacting with the Website URL, if the URL is unique every time it is clicked, it is a dynamic webpage.

Using a Template Plugin App, in the Redirect field, try entering just the first part of the link the app redirects to upon landing, the domain name: “https://login.exampledomain.com

Example domain name

    • It does not matter if the deep links of the redirect URL change dynamically whenever trying to connect. They will always match the domain name part.
    • If that does not work, as a possible workaround, if the login form is built in an iframe HTML element, sometimes Setting up a SWA App Using a Template Frame Plugin App will allow a dynamic webpage to work.


Related References

Loading
SWA App Does Not Autofill Credentials