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 #107] Auth with SSO - fields 'discoverable_by_name' and 'discoverable_by_email' #5979

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

Originally created by @abonanni on GitHub (Jan 26, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/107

Description

The fields 'discoverable_by_email' and 'discoverable_by_name' are resetted to 0 in the databases when a user log in whit SSO.

And we have the same issue with 'frontend_settings' field.

Vikunja Frontend Version

0.22.0

Vikunja API Version

0.22.0

Browser and version

FF 122

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @abonanni on GitHub (Jan 26, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/107 ### Description The fields 'discoverable_by_email' and 'discoverable_by_name' are resetted to 0 in the databases when a user log in whit SSO. And we have the same issue with 'frontend_settings' field. ### Vikunja Frontend Version 0.22.0 ### Vikunja API Version 0.22.0 ### Browser and version FF 122 ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror added the bug label 2026-04-20 16:27:27 -05:00
GiteaMirror commented 2026-04-20 16:27:30 -05:00
Author
Owner
Copy Link

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

Are you able to reproduce this with the latest unstable build?

<!-- gh-comment-id:1912463226 --> @kolaente commented on GitHub (Jan 26, 2024): Are you able to reproduce this with the latest unstable build?
GiteaMirror commented 2026-04-20 16:27:30 -05:00
Author
Owner
Copy Link

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

Fixed for me with:

Frontend Version: 0.22.0+89-30d599369f

API Version: v0.22.0+32-d38050f2b8

<!-- gh-comment-id:1913364186 --> @Spiritreader commented on GitHub (Jan 27, 2024): Fixed for me with: Frontend Version: 0.22.0+89-30d599369f API Version: v0.22.0+32-d38050f2b8
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#5979
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?