You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was tested with the latest Chrome 103 and Firefox 101 on NC24.0.2.
Registering the Trustkey with Chrome 103 for FIDO2 or 2FA doesn't work, because the public_key_credential_id field in oc_twofactor_webauthn_registrations and oc_webauthn are only VARCHAR(255), while the string to be stored is 256 bytes long.
After resizing the column in both tables, both FIDO2 and 2FA logins work from Firefox or Chrome.
The text was updated successfully, but these errors were encountered:
ALTER TABLE oc_twofactor_webauthn_registrations ALTER COLUMN public_key_credential_id TYPE VARCHAR(256);
ALTER TABLE oc_webauthn ALTER COLUMN public_key_credential_id TYPE VARCHAR(256);
The standard does not mandate a maximum size for credential ids. We only tested this using Yubikeys and their keys always fitted inside the table column.
I guess we should increase the width of the column.
This was tested with the latest Chrome 103 and Firefox 101 on NC24.0.2.
Registering the Trustkey with Chrome 103 for FIDO2 or 2FA doesn't work, because the public_key_credential_id field in oc_twofactor_webauthn_registrations and oc_webauthn are only VARCHAR(255), while the string to be stored is 256 bytes long.
After resizing the column in both tables, both FIDO2 and 2FA logins work from Firefox or Chrome.
The text was updated successfully, but these errors were encountered: