github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 19:47:47 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #99] Restoring OpenID users is a problem #5965

New Issue
Closed
opened 2026-04-20 16:25:36 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-20 16:25:36 -05:00
Owner
Copy Link

Originally created by @aleprovencio on GitHub (Dec 8, 2023).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/99

Description

Hi,

I have my vikunja configured to use authelia's OpenID, and this is way I authenticate.

I was first surprised that I could not set a password for this account and also about the fact that it is not possible to link this account with other existing accounts.

I usually use this approach in other apps so I'm still able to log in without having to authenticate via authelia.

But anyways, authenticating with authelia was working fine, until I needed to restore the database from a backup.

The restoring process is fine, but when I try to connect to the restored account, vikunja creates a new one, so I'm locked out.

I've also tried changing the password for this account via the CLI, but that also results in an error.

Vikunja Frontend Version

0.21.0

Vikunja API Version

0.21.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @aleprovencio on GitHub (Dec 8, 2023). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/99 ### Description Hi, I have my `vikunja` configured to use `authelia`'s `OpenID`, and this is way I authenticate. I was first surprised that I could not set a password for this account and also about the fact that it is not possible to link this account with other existing accounts. I usually use this approach in other apps so I'm still able to log in without having to authenticate via `authelia`. But anyways, authenticating with `authelia` was working fine, until I needed to restore the database from a backup. The restoring process is fine, but when I try to connect to the restored account, `vikunja` creates a new one, so I'm locked out. I've also tried changing the password for this account via the `CLI`, but that also results in an error. ### Vikunja Frontend Version 0.21.0 ### Vikunja API Version 0.21.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror added the bug label 2026-04-20 16:25:36 -05:00
GiteaMirror commented 2026-04-20 16:25:38 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 12, 2023):

Just to confirm I understood you correctly: You restored your Vikunja instance from a backup and when you now try to log in again, you now have a new user instead of the existing one?

If that's the case, can you check if the issuer and subject in the users table are different for the old and new user?

<!-- gh-comment-id:1852837400 --> @kolaente commented on GitHub (Dec 12, 2023): Just to confirm I understood you correctly: You restored your Vikunja instance from a backup and when you now try to log in again, you now have a new user instead of the existing one? If that's the case, can you check if the `issuer` and `subject` in the `users` table are different for the old and new user?
GiteaMirror commented 2026-04-20 16:25:39 -05:00
Author
Owner
Copy Link

@aleprovencio commented on GitHub (Dec 13, 2023):

Yes it does create a new user, where issuer records are the same (authelia.mydomain) but subject ones are not.

<!-- gh-comment-id:1853811662 --> @aleprovencio commented on GitHub (Dec 13, 2023): Yes it does create a new user, where `issuer` records are the same (`authelia.mydomain`) but `subject` ones are not.
GiteaMirror commented 2026-04-20 16:25:41 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 13, 2023):

The subject is taken from the openID provider. If it's different in the database that means your provider has changed it.

<!-- gh-comment-id:1854327379 --> @kolaente commented on GitHub (Dec 13, 2023): The subject is taken from the openID provider. If it's different in the database that means your provider has changed it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label bug
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#5965
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?