github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-03-12 10:04:48 -05:00
Code Issues 219 Packages Projects Releases 2 Wiki Activity

Unable to enable two factor authentication with new install on latest version (v1.0.0-rc1) #591

New Issue
Closed
opened 2025-11-01 20:59:52 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-01 20:59:52 -05:00
Owner
Copy Link

Originally created by @TheDave94 on GitHub (Sep 3, 2025).

Description

In a new install I can't enable two factor authentication. The logs show “This account is managed by a third-party authentication provider” (Error Code 1021). I tried really everything to solve it but the only solution was to go back to v0.24.6 which worked immediately. For potential troubleshooting see my attached extensive troubleshooting with AI:
https://www.perplexity.ai/search/9a86d119-fd1b-4796-8708-63a0c3b07472
I am aware that a similar issue has been already opened here but since it was closed as resolved I thought it would be better to open a new one.

Vikunja Version

1.0.0-rc1

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @TheDave94 on GitHub (Sep 3, 2025). ### Description In a new install I can't enable two factor authentication. The logs show “This account is managed by a third-party authentication provider” (Error Code 1021). I tried really everything to solve it but the only solution was to go back to v0.24.6 which worked immediately. For potential troubleshooting see my attached extensive troubleshooting with AI: https://www.perplexity.ai/search/9a86d119-fd1b-4796-8708-63a0c3b07472 I am aware that a similar issue has been already opened here but since it was closed as resolved I thought it would be better to open a new one. ### Vikunja Version 1.0.0-rc1 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2025-11-01 20:59:53 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 3, 2025):

Are you using local auth? Or a third party auth provider? (ldap or openid)

@kolaente commented on GitHub (Sep 3, 2025): Are you using local auth? Or a third party auth provider? (ldap or openid)
GiteaMirror commented 2025-11-01 20:59:53 -05:00
Author
Owner
Copy Link

@TheDave94 commented on GitHub (Sep 3, 2025):

I use only local auth. I've been through all the possible configurations and database errors for hours. Turns out I had it right from the beginning because it just works with the latest stable.

@TheDave94 commented on GitHub (Sep 3, 2025): I use only local auth. I've been through all the possible configurations and database errors for hours. Turns out I had it right from the beginning because it just works with the latest stable.
GiteaMirror commented 2025-11-01 20:59:54 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 3, 2025):

But it does not work with the current unstable build? Because we'd still need to fix it in that case - the next version will be cut from the current unstable branch.

@kolaente commented on GitHub (Sep 3, 2025): But it does not work with the current unstable build? Because we'd still need to fix it in that case - the next version will be cut from the current unstable branch.
GiteaMirror commented 2025-11-01 20:59:54 -05:00
Author
Owner
Copy Link

@TheDave94 commented on GitHub (Sep 4, 2025):

I just tried unstable and got the same error. I'm happy to help testing, will stay on the unstable branch for now.

@TheDave94 commented on GitHub (Sep 4, 2025): I just tried unstable and got the same error. I'm happy to help testing, will stay on the unstable branch for now.
GiteaMirror commented 2025-11-01 20:59:54 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 4, 2025):

Will be fixed by https://github.com/go-vikunja/vikunja/pull/1414

@kolaente commented on GitHub (Sep 4, 2025): Will be fixed by https://github.com/go-vikunja/vikunja/pull/1414
GiteaMirror commented 2025-11-01 20:59:55 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 4, 2025):

Fixed in https://github.com/go-vikunja/vikunja/pull/1414, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Sep 4, 2025): Fixed in https://github.com/go-vikunja/vikunja/pull/1414, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
GiteaMirror commented 2025-11-01 20:59:55 -05:00
Author
Owner
Copy Link

@TheDave94 commented on GitHub (Sep 4, 2025):

Thanks this fixed it

@TheDave94 commented on GitHub (Sep 4, 2025): Thanks this fixed it
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/caldav
area/filters
area/frontend
area/gantt
area/internal-code
area/typesense
bug
changes requested
confirmed
dependencies
enhancement
good first issue
help wanted
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#591
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?