[GH-ISSUE #2405] Issues with OIDC and passkeys on Desktop #6668

Closed
opened 2026-04-20 17:15:31 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @remilapeyre on GitHub (Mar 17, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2405

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

Hello, I have been using Vikunja with OIDC configured and my OIDC provider has 2FA with passkeys enabled.

Because the login webview opens directly in the application the authentication flow fails while waiting for the passkey.

The auth form is also not recognized by 1Password.

I think it might be better to open the webbrowser to complete the authentication flow instead of doing it directly in the application. It would solve both problems.

Vikunja Version

2.1.0

Browser and version

Desktop

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @remilapeyre on GitHub (Mar 17, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2405 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description Hello, I have been using Vikunja with OIDC configured and my OIDC provider has 2FA with passkeys enabled. Because the login webview opens directly in the application the authentication flow fails while waiting for the passkey. The auth form is also not recognized by 1Password. I think it might be better to open the webbrowser to complete the authentication flow instead of doing it directly in the application. It would solve both problems. ### Vikunja Version 2.1.0 ### Browser and version Desktop ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
Author
Owner

@kolaente commented on GitHub (Mar 17, 2026):

Once we have https://github.com/go-vikunja/vikunja/pull/2308 we can rebuild the desktop app so that it uses the same mechanism.

<!-- gh-comment-id:4077051744 --> @kolaente commented on GitHub (Mar 17, 2026): Once we have https://github.com/go-vikunja/vikunja/pull/2308 we can rebuild the desktop app so that it uses the same mechanism.
Author
Owner

@kolaente commented on GitHub (Mar 30, 2026):

https://github.com/go-vikunja/vikunja/pull/2308 and follow up https://github.com/go-vikunja/vikunja/pull/2500 are both merged, this should be fixed now. Please check with the latest unstable build (both desktop and api) to see if your problem went away.

<!-- gh-comment-id:4158591907 --> @kolaente commented on GitHub (Mar 30, 2026): https://github.com/go-vikunja/vikunja/pull/2308 and follow up https://github.com/go-vikunja/vikunja/pull/2500 are both merged, this should be fixed now. Please check with the latest unstable build (both desktop and api) to see if your problem went away.
Author
Owner

@remilapeyre commented on GitHub (Mar 31, 2026):

Thanks, it does work now :)

<!-- gh-comment-id:4162254157 --> @remilapeyre commented on GitHub (Mar 31, 2026): Thanks, it does work now :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6668