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 #102] Resetting user preferences during login #5970

New Issue
Closed
opened 2026-04-20 16:26:18 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-20 16:26:18 -05:00
Owner
Copy Link

Originally created by @liamgilbey on GitHub (Dec 22, 2023).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/102

Description

I have an issue where Vikjuna is resetting user preferences when they login.

I have setup Vikjuna with OIDC integration handled by Authelia, and I can successfully login and update user preferences. My setup is with MariaDB, and I can confirm a value in the database is updated when a user preference is changed.

image

However, if that users logs out and in again, that preference is gone

image

I've reviewed the MariaDB logs and I can see the following happening:


UPDATE `users` SET `name` = '<user>', `username` = '<username>', `email` = '<email>', `avatar_provider` = '', `avatar_file_id` = 0, `email_reminders_enabled` = 0, `discoverable_by_name` = 0, `discoverable_by_email` = 0, `overdue_tasks_reminders_enabled` = 0, `overdue_tasks_reminders_time` = '9:00', `default_project_id` = 0, `week_start` = 0, `language` = 'en', `timezone` = 'Pacific/Auckland', `frontend_settings` = '{\"color_schema\":\"auto\",\"play_sound_when_done\":true,\"quick_add_magic_mode\":\"vikunja\"}', `updated` = '2023-12-22 17:34:54' WHERE `id`=1

It's as if every time a user logs on, the api is treating them like a new user.

Vikunja Frontend Version

0.22.0

Vikunja API Version

0.22.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @liamgilbey on GitHub (Dec 22, 2023). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/102 ### Description I have an issue where Vikjuna is resetting user preferences when they login. I have setup Vikjuna with OIDC integration handled by Authelia, and I can successfully login and update user preferences. My setup is with MariaDB, and I can confirm a value in the database is updated when a user preference is changed. ![image](https://github.com/go-vikunja/api/assets/8405101/71e75376-577d-415e-bac6-a0952f2bfaa7) However, if that users logs out and in again, that preference is gone ![image](https://github.com/go-vikunja/api/assets/8405101/95617b06-008c-4e0a-8c13-b636d3bead9c) I've reviewed the MariaDB logs and I can see the following happening: ```sql UPDATE `users` SET `name` = '<user>', `username` = '<username>', `email` = '<email>', `avatar_provider` = '', `avatar_file_id` = 0, `email_reminders_enabled` = 0, `discoverable_by_name` = 0, `discoverable_by_email` = 0, `overdue_tasks_reminders_enabled` = 0, `overdue_tasks_reminders_time` = '9:00', `default_project_id` = 0, `week_start` = 0, `language` = 'en', `timezone` = 'Pacific/Auckland', `frontend_settings` = '{\"color_schema\":\"auto\",\"play_sound_when_done\":true,\"quick_add_magic_mode\":\"vikunja\"}', `updated` = '2023-12-22 17:34:54' WHERE `id`=1 ``` It's as if every time a user logs on, the api is treating them like a new user. ### Vikunja Frontend Version 0.22.0 ### Vikunja API Version 0.22.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:26:20 -05:00
Author
Owner
Copy Link

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

It's as if every time a user logs on, the api is treating them like a new user.

Can you verify if the user is created on every login?

<!-- gh-comment-id:1867969961 --> @kolaente commented on GitHub (Dec 22, 2023): > It's as if every time a user logs on, the api is treating them like a new user. Can you verify if the user is created on every login?
GiteaMirror commented 2026-04-20 16:26:22 -05:00
Author
Owner
Copy Link

@liamgilbey commented on GitHub (Dec 22, 2023):

From the database perspective, it's not. I can see the user list is not growing, and instead the record has all attributes reset as in the SQL query above. I can also see the created column stays the same, but the updated column is updated with the timestamp of the login

<!-- gh-comment-id:1867997762 --> @liamgilbey commented on GitHub (Dec 22, 2023): From the database perspective, it's not. I can see the user list is not growing, and instead the record has all attributes reset as in the SQL query above. I can also see the `created` column stays the same, but the `updated` column is updated with the timestamp of the login
GiteaMirror commented 2026-04-20 16:26:25 -05:00
Author
Owner
Copy Link

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

Looks like this only happened when the user's name or email had changed in the external auth provider.

Should be fixed in a5a6aba7c8. Please check with the next unstable build if your problem went away.

<!-- gh-comment-id:1869041046 --> @kolaente commented on GitHub (Dec 25, 2023): Looks like this only happened when the user's name or email had changed in the external auth provider. Should be fixed in a5a6aba7c80618a45bb57616c7378917675cadab. Please check with the next unstable build if your problem went away.
GiteaMirror commented 2026-04-20 16:26:28 -05:00
Author
Owner
Copy Link

@liamgilbey commented on GitHub (Dec 25, 2023):

I can confirm that works nicely - thank you

<!-- gh-comment-id:1869081892 --> @liamgilbey commented on GitHub (Dec 25, 2023): I can confirm that works nicely - thank you
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
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#5970
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?