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

[GH-ISSUE #108] Changing data in SSO provider resets the entire configuration object #5980

New Issue
Closed
opened 2026-04-20 16:27:30 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 16:27:30 -05:00
Owner
Copy Link

Originally created by @Spiritreader on GitHub (Jan 27, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/108

Description

Hello!

When a user changes their e-mail address in the SSO provider, the respective database object in vikunja gets updated as expected. (Checked with pgadmin by querying the user table before and after)
However, all other user configurable settings are reset to default in the process.
For example avatar configuration, visibility options, week start date etc.

Ideally, it would be awesome if only the fields are changed that are actually updated via the SSO provider.
Not a big issue in any way, just stumbled across this when I updated my e-mail in authentik.

Vikunja Frontend Version

0.22.0

Vikunja API Version

v0.22.0

Browser and version

Firefox 123.03b

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @Spiritreader on GitHub (Jan 27, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/108 ### Description Hello! When a user changes their e-mail address in the SSO provider, the respective database object in vikunja gets updated as expected. (Checked with pgadmin by querying the user table before and after) However, all other user configurable settings are reset to default in the process. For example avatar configuration, visibility options, week start date etc. Ideally, it would be awesome if only the fields are changed that are actually updated via the SSO provider. Not a big issue in any way, just stumbled across this when I updated my e-mail in authentik. ### Vikunja Frontend Version 0.22.0 ### Vikunja API Version v0.22.0 ### Browser and version Firefox 123.03b ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:27:32 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 27, 2024):

Duplicate of https://github.com/go-vikunja/api/issues/107

<!-- gh-comment-id:1913352789 --> @kolaente commented on GitHub (Jan 27, 2024): Duplicate of https://github.com/go-vikunja/api/issues/107
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#5980
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?