workspaces-issues
workspaces-issues copied to clipboard
Missing totp 2fa in version 1.15
There is no totp menu in two-factor-setup (fresh installation of kasm_release_1.15.0.06fdc8 on a debian 12 vm), though the option "allow_totp_2fa" is enabled in settings for all users. I only have the possibility to use webauthn.
Can you please try deleting the allow_totp_2fa setting from the All Users group and then re-adding it.
Hopefully that should correct the issue
yes I have the same issue that I only have the webauthn, in my 1.14.0 which was upgrade from 1.13.0 I can use the Google authentication
Can you please try deleting the
allow_totp_2fasetting from the All Users group and then re-adding it. Hopefully that should correct the issue in 1.14.0 it is actually called "enable_totp_two_factor"
yes I have the same issue that I only have the webauthn, in my 1.14.0 which was upgrade from 1.13.0 I can use the Google authentication
This is no direct support for webauthn in 1.14. Its only TOTP. In either case, both of these options only apply to local or LDAP based auth. If you are using SAML or OIDC then these settings are ignored since the MFA is handled by the identity provider
No I meant that in verson 1.14.0 it is called "enable_totp_two_factor" while on my new test setup in 1.15.0 it is "allow_totp_2fa". In 1.15.0 I did remove it and re-added it and it was working. only the QR code seems to be not so easy to scan with my app. I took a screenshot and paste it into a paint program and that way I could scan the QR. could that be made a big bigger maybe. because when I setup 2FA for SSH in the CLi it is huge and always reliable to scan.
In the default install "allow_totp_2fa" is of type string. When you remove and add "allow_totp_2fa" it's now of type boolean and setting it to true gets you the TOTP 2fa option again.
Confirmed @mathiasringhof's fix works on a fresh KASM 1.15.0 install.
Removing it and re-adding it resolved this issue for me. Very weird problem on a fresh install.