Codeberg/Community
60
387
Fork
You've already forked Community
12

Failed two factor authentication (usb key) #1136

Closed
opened 2023年08月11日 12:47:16 +02:00 by cage · 5 comments

Hi!

I was not able to login using my USB device as second factor authentication as i made before. I can confirm that the device is working as I successfully logged in on another website, with the same computer, the same OS and browser (linux, firefox 115.1.0esr).

Thanks in advance for your help!
C.

Hi! I was not able to login using my USB device as second factor authentication as i made before. I can confirm that the device is working as I successfully logged in on another website, with the same computer, the same OS and browser (linux, firefox 115.1.0esr). Thanks in advance for your help! C.
cage changed title from (削除) failed two factor authentication (usb key) (削除ここまで) to Failed two factor authentication (usb key) 2023年08月11日 12:47:47 +02:00

Hi @cage,

Which hardware token are you using, if it's an solokey or nitrokey this is likely an duplicate of #1119

Hi @cage, Which hardware token are you using, if it's an solokey or nitrokey this is likely an duplicate of https://codeberg.org/Codeberg/Community/issues/1119
Author
Copy link

Hi!

Thanks for your prompt reply!

Unfortunately my device is neither a nitrokey nor a solokey. It is a winkeo fido2. I am just reading the thread you linked, thanks, and i can say that even on chromium i get an error that the device is not registered with codeberg.

I am going to change the firefox configuration as suggested on nitrokey forum and report back the results.

Thank you!
c.

Hi! Thanks for your prompt reply! Unfortunately my device is neither a nitrokey nor a solokey. It is a winkeo fido2. I am just reading the thread you linked, thanks, and i can say that even on chromium i get an error that the device is not registered with codeberg. I am going to change the firefox configuration as suggested on nitrokey forum and report back the results. Thank you! c.
Author
Copy link

Hi @Gusted

After setting to false the variable security.webauthn.ctap2 the login works flawlessy!

Anyway i feel i have to highlight that even with the aforementioned variable set to true i was able to login on another website, could this possibly be related to different procedures (different library, perhaps) that the two website are using in the backend infrastructure?

Do you think this issue should be forwarded upstream before closing it, or just closing this report is OK?

Bye!
C.

Hi @Gusted After setting to `false` the variable `security.webauthn.ctap2` the login works flawlessy! Anyway i feel i have to highlight that even with the aforementioned variable set to `true` i was able to login on another website, could this possibly be related to different procedures (different library, perhaps) that the two website are using in the backend infrastructure? Do you think this issue should be forwarded upstream before closing it, or just closing this report is OK? Bye! C.

, could this possibly be related to different procedures (different library, perhaps) that the two website are using in the backend infrastructure?

Yeah, Forgejo (software that's running Codeberg.org) use more strict but the more recommended WebAuthn options, which are causing problems with newer versions of Firefox in combination with some security keys.

Do you think this issue should be forwarded upstream before closing it, or just closing this report is OK?

We're already tracking this issue at #1119, so I'm going to close this one and comment on the other issue that winkeo fido2 is also affected.

> , could this possibly be related to different procedures (different library, perhaps) that the two website are using in the backend infrastructure? Yeah, Forgejo (software that's running Codeberg.org) use more strict but the more recommended WebAuthn options, which are causing problems with newer versions of Firefox in combination with some security keys. > Do you think this issue should be forwarded upstream before closing it, or just closing this report is OK? We're already tracking this issue at https://codeberg.org/Codeberg/Community/issues/1119, so I'm going to close this one and comment on the other issue that `winkeo fido2` is also affected.
Author
Copy link

Hi!

Yeah, Forgejo (software that's running Codeberg.org) use more strict but the more recommended WebAuthn options, which are causing problems with newer versions of Firefox in combination with some security keys.

Uh, I see! This makes totally sense to me, thanks for your explanation!

Bye!
C.

Hi! > Yeah, Forgejo (software that's running Codeberg.org) use more strict but the more recommended WebAuthn options, which are causing problems with newer versions of Firefox in combination with some security keys. Uh, I see! This makes totally sense to me, thanks for your explanation! Bye! C.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug
Something is not working the way it should. Does not concern outages.
bug
infrastructure
 Errors evidently caused by infrastructure malfunctions or outages
Codeberg
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome
Please join the discussion and consider contributing a PR!
docs
No bug, but an improvement to the docs or UI description will help
duplicate
This issue or pull request already exists
enhancement
New feature
infrastructure
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal
An issue directly involving legal compliance
licence / ToS
involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
 Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations
Things related to Codeberg's external communication
question
More information is needed
question
user support
 This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo
Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration
Migration related issues in Forgejo
s/Pages
Issues related to the Codeberg Pages feature
s/Weblate
Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker
Woodpecker CI related issue
security
involves improvements to the sites security
service
Add a new service to the Codeberg ecosystem (instead of implementing into Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, etc.)
wontfix
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1136
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?