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

OpenID: Name is reset to username on every login #2035

New Issue
Closed
opened 2026-03-22 13:52:03 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-22 13:52:03 -05:00
Owner
Copy Link

Originally created by @baltitenger on GitHub (Nov 16, 2024).

Description

As the title says. This is confusing because vikunja still allows the user to change their name, which will persist until the next time they do a fresh login. (Also, I think it should use the name field instead of preferred_username for the initial value of the user's display name)

Vikunja Version

v0.24.4

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @baltitenger on GitHub (Nov 16, 2024). ### Description As the title says. This is confusing because vikunja still allows the user to change their name, which will persist until the next time they do a fresh login. (Also, I think it should use the `name` field instead of `preferred_username` for the initial value of the user's display name) ### Vikunja Version v0.24.4 ### 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-03-22 13:52:03 -05:00
GiteaMirror commented 2026-03-22 13:52:04 -05:00
Author
Owner
Copy Link

@baltitenger commented on GitHub (Nov 17, 2024):

Hmm, apparently it does use the name field but the OpenID provider I'm using (forgejo) uses the username in the name field for the id_token but not for the userinfo response...

@baltitenger commented on GitHub (Nov 17, 2024): Hmm, apparently it does use the `name` field but the OpenID provider I'm using (forgejo) uses the username in the name field for the id_token but not for the userinfo response...
GiteaMirror commented 2026-03-22 13:52:05 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 18, 2024):

Looks like the solution here is to disable changing the name in user settings.

@kolaente commented on GitHub (Nov 18, 2024): Looks like the solution here is to disable changing the name in user settings.
GiteaMirror commented 2026-03-22 13:52:06 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 21, 2025):

Fixed in 090dd4b2f6, please check with the next unstable build (should be ready for deployment in ~45min, also on try).

@kolaente commented on GitHub (Jan 21, 2025): Fixed in 090dd4b2f60078a84052591a5f3bed8907da21e3, please check with the next unstable build (should be ready for deployment in ~45min, also on [try](https://try.vikunja.io)).
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#2035
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?