GregH.82552 (Customer) asked a question.
Issues with Okta browser plugin after updating to chrome version 126.0.6478.62
After updating chrome browser to 126 release, users are not able to Disable browser password prompts in settings for the Okta browser plugin. The user is presented with "This feature is not available because your privacy related settings are managed by your organization or another extension." Without being able to disable the browser password prompts, users need to log into each auto launch tab separately. Everything was working as expected until the chrome update.....
Hi @GregH.82552 (Customer) , Thank you for reaching out to the Okta Community!
As of now, I have not seen any reports of issues with the Okta Browser Plugin.
I tried to reproduce the issue and it seems to be working on my end (MacOS - Sonoma 14.5 ).
> Version 125.0.6422.142 (Official Build) (arm64) - the Okta Plugin seems to be workin as expected
> while checking the browser version it triggered the auto-update - now on Version 126.0.6478.62 (Official Build) (arm64) - still seems to be working as expected.
I did some digging through the older reports and found a similar thing that mentioned mixed results.
One was referencing the "Reset Plugin" option (from the plugin's menu) on the end-user sides.
The other mentioned that toggling the option from Okta Admin dashboard → Applications → Self service → Allow users to add personal apps which seems to be tied into the "Disable browser prompts" feature.
All that being said, if you have an account with us I would recommend opening a case to work with my Support colleagues to investigate the issue in case we're dealing with something new, that we don't know about caused by the recent browser update.
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
I am sorry that I failed to mention that we are currently seeing this issue on devices running windows 10 21H2 Enterprise Edition LTSC. The issue came about when updating a user's laptop and chrome updated to 126. As a means to troubleshoot the issue, we then updated chrome on a desktop running windows 10 21H2 Enterprise Edition LTSC and had the same result. Users can go and clear browsing data, close all windows, then re-open chrome browser and the Okta plugin will work as expected. Once the user closes the browser (without clearing the browsing history) and opens a new browser, the issue returns.
Thank you for the additional details! This should be helpful for anyone else in the Community that might be experiencing the same.
In the meantime, I recommend connecting with my colleagues from the Support Team to have this investigated.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.