nextcloud / nextcloud/twofactor_webauthn
Trustkey G310 registration doesn't work on Chrome
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 59
- Forks
- 11
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 16
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the reported public_key_credential_id columns in oc_twofactor_webauthn_registrations and oc_webauthn as the starting point. Verify the registration path with Chrome 103 and Firefox 101 on Nextcloud 24.0.2, and confirm that both FIDO2 and 2FA logins work when the columns accept the 256-byte value.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, databases, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100