
ex4xr (ex4xr) asked a question.
We have a user that show internal error every times when he want to sign in to OKTA via Edge.
We installed the Chrome for him, set it as the default browser and everything was good for the web application.
however, for MS Team, the default pop out browser should still is Edge and show that error.
Anyway i can make the pop out authentication page to Chrome? thank you.

Hello @ex4xr (ex4xr)
Thanks for posting.
The Okta Browser Plugin enables you to automatically sign into applications that would otherwise require you to manually enter your credentials (e.g., applications that do not support SAML or a direct form POST to a URL). Using the plugin enables you to use SSO for a broader range of applications.
When end users start an app from their Okta End User Dashboard, a new browser tab opens to the app's URL. The plugin uses an encrypted SSL connection to obtain authentication information and other required information from Okta, and then applies that information to the page. The plugin does not store their credentials after authentication is complete.
Please follow this document to download the Chrome Browser plugin and get additional information:
https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Browser_Plugin.htm
Configure browsers for single sign-on on Windows:
https://help.okta.com/en/prod/Content/Topics/Directory/ad-dsso-migrate-configure-browser.htm
Let us know if this helps you.
Have a great day!
Daniela Chavarria.
Okta Inc.
Ricky's referring to the browser window that Microsoft Teams displays when Microsoft redirects the user to Okta for authentication. It has nothing to do with the Okta plug in or the dashboard.
We have some users that experience this same issue. We recently started rolling out the Palo Alto Global Protect VPN client, and for a small number of users, when that client tries to authenticate, it pops open a small browser window (IE or Edge, regardless of the user's default browser), which almost immediately generates a script error, preventing the user from signing in. Sometimes, clearing the IE/Edge cache and temporary files will fix it, but not always. One user had the problem follow him from PC to PC to PC. Another thing to try is to open an IE/Edge browser and sign into your Okta dashboard and THEN launch Teams, so when it tries to authenticate, there's already an active, authenticated session running. That's not a long term solution, clearly.