Issue with 2FA / Google Authenticator secret key after upgrade to 26.3.11.9650

Avatar
  • updated
  • Open

Hello,

Following the upgrade of our on-premises installation to version 26.3.11.9650, we are experiencing an issue with the settings of several user accounts.

We have selected "Google Authenticator" as the 2FA method and entered the secret key. However, after saving and reopening the user account details, the secret key field appears empty. If we click "Save" again, the system prompts us for the secret key. If we close the window without saving instead, the user is still able to log in using the hidden/invisible secret key.

This issue occurs with many, but not all, of our user accounts.

Deleting and recreating the user accounts did not resolve the issue.

Avatar
0
Dirk Mühlmann

Hello Sean,

thanks for your reply.

It's good to know that you're already working on a solution.

Dirk

Avatar
2
Sean White Team Member

Dirk, 
Thanks for your report. This is a Known Issue and is slated for release with 26.5 which is expected to be stable in approximately 3 weeks.