Significant hindrances to usability:

1. Seemingly oblivious to container tabs - all shortcuts open in the default container, despite not even having an authenticated session present there.

2. Does not appear to provide any kind of unification for single-sign-on. Again shortcuts opened into the default container, then required me to re-enter my password as there was no existing authenticated session. It also did not bridge or forward the authorization captured by the extension from a different container.

3. Supposed keyboard shortcut conflicts with a bookmark menu shortcut and does not work.

Ultimately, I'm not sure what this provides beyond a 'cute' mirror of the Okta dashboard...

after some time the plugin will freeze the gui on the top right and it will not dissapear. Only way to to solve is to remove the plugin and reinstall. Very annoying

New version requires "Read and modify privacy settings". Hi Okta, I know you mean well but please lets take a moment and put yourself in users` shoes:
There is this app that you sometimes use to make things a bit more convenient. It's not the only way to get things done but it's one of the fastest ones. Now that app needs to gain control about YOUR privacy settings. The privacy controls that is the last tiny bit you can still control on the internet. And this app want's to have the ability to modify things behind the curtains. I'm gonna go with a "Hefty no to that." Even at the cost of uninstalling it..

Edit:
Thank you for your explanation. I do appreciate when developers follow up. Unfortunately (for me), I am not willing to provide that permission. If anything, the internet thought me that privacy cannot be based on honor system.

It was not comfortable to require it to be installed in the first place, but I could live with it.
What has become a show-stopper is that latest versions require it to be given "Read and modify privacy settings".
That is a permission I am not willing to give to any extension.

The Okta Browser Plugin doesn't respect Firefox Containers and always launches in the 'Default' Container.

If you're using Okta for AWS Account access via SAML as I am. This is a bit tedious.

You can only access several AWS accounts via SAML if you launch them in seperate containers/profiles/browsers. I managed this via Firefox Containers but, without this support, the Okta Browser Plugin is rather useless. I'm better off using the web UI directly.