Remote Help Application Shows a Blank Okta Login Page

When attempting to log in with a federated account through the Remote Help or Quick Assist application within Windows, the Okta login page renders partially blank after selecting the federated Microsoft account. This occurs because the embedded browser within the application lacks support for specific HTML standards required by the default Okta sign-in widget. Applying the third-generation Okta sign-in widget resolves this issue by using simpler code that is compatible with feature-limited browsers.

• Okta Identity Engine (OIE)
• Remote Help
• Quick Assist
• Microsoft Office
• Federated Login

The embedded browser within Remote Help and Quick Assist does not support specific HTML standards utilized by the default Okta sign-in widget.

How is the blank login page issue resolved?

The blank login page is a limitation of the Microsoft WebView2 embedded browser. Applying the third-generation sign-in widget to the Okta tenant resolves this issue. This version of the widget uses simpler code that is more compatible with feature-limited browsers and screen-reader software.

NOTE: This widget generation is available with Okta Identity Engine (OIE) but not in Okta Classic Engine tenants. Other limitations apply to the third-generation sign-in widget. Review the sign-in widget (third-generation) documentation tto understand any potential impact on the organization before implementation. Implementing the third-generation sign-in widget is a tenant-wide change that impacts most other applications.