github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-15 22:32:29 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

OIDC - "It looks like your openid configuration is in the wrong format. Please check the docs for the correct format." #601

New Issue
Closed
opened 2025-11-01 21:00:06 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-01 21:00:06 -05:00
Owner
Copy Link

Originally created by @Lipown on GitHub (Sep 9, 2025).

Description

Using docker compose installation I updated the Vikunja and started to get this error in container when I try to log in.

I am using Authentik for OIDC and it was working without issues for at least a year.
I am stuck on this screen.

Image

Vikunja Version

image: vikunja/vikunja

Browser and version

Tried different browsers, different platforms

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @Lipown on GitHub (Sep 9, 2025). ### Description Using docker compose installation I updated the Vikunja and started to get this error in container when I try to log in. I am using Authentik for OIDC and it was working without issues for at least a year. I am stuck on this screen. <img width="1095" height="887" alt="Image" src="https://github.com/user-attachments/assets/e387fa95-20ba-40d5-b47d-83ccf475908f" /> ### Vikunja Version image: vikunja/vikunja ### Browser and version Tried different browsers, different platforms ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2025-11-01 21:00:07 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 9, 2025):

You need to migrate your config to the new format. It seems like you upgraded to the newest RC which requires that.

Check out the docs about this: https://vikunja.io/docs/openid/#step-2-configure-vikunja

@kolaente commented on GitHub (Sep 9, 2025): You need to migrate your config to the new format. It seems like you upgraded to the newest RC which requires that. Check out the docs about this: https://vikunja.io/docs/openid/#step-2-configure-vikunja
GiteaMirror commented 2025-11-01 21:00:07 -05:00
Author
Owner
Copy Link

@tszdabee commented on GitHub (Sep 12, 2025):

You need to migrate your config to the new format. It seems like you upgraded to the newest RC which requires that.

Check out the docs about this: https://vikunja.io/docs/openid/#step-2-configure-vikunja

@kolaente thanks, updating the config worked :)

@tszdabee commented on GitHub (Sep 12, 2025): > You need to migrate your config to the new format. It seems like you upgraded to the newest RC which requires that. > > Check out the docs about this: https://vikunja.io/docs/openid/#step-2-configure-vikunja @kolaente thanks, updating the config worked :)
GiteaMirror commented 2025-11-01 21:00:08 -05:00
Author
Owner
Copy Link

@VincentSC commented on GitHub (Sep 22, 2025):

Well, it only works when using the "unstable syntax", as the other syntax has been dropped.

auth:
  openid:
    enabled: true
    providers:
       <provider-id>:
          name: <provider-name>
          authurl: <auth-url>  <----- Used for OIDC Discovery, usually the issuer
          clientid: <vikunja client-id>
          clientsecret: <vikunja client-secret>
          scope: openid profile email
          forceuserinfo: false # Optional: Set to true to always use UserInfo endpoint instead of ID token claims, defaults to false

Supporting the "stable syntax" is set not will-not-fix, as discussed in https://github.com/go-vikunja/vikunja/issues/1533 and documentation still needs to be updated.

@VincentSC commented on GitHub (Sep 22, 2025): Well, it only works when using the "unstable syntax", as the other syntax has been dropped. ``` auth: openid: enabled: true providers: <provider-id>: name: <provider-name> authurl: <auth-url> <----- Used for OIDC Discovery, usually the issuer clientid: <vikunja client-id> clientsecret: <vikunja client-secret> scope: openid profile email forceuserinfo: false # Optional: Set to true to always use UserInfo endpoint instead of ID token claims, defaults to false ``` Supporting the "stable syntax" is set not will-not-fix, as discussed in https://github.com/go-vikunja/vikunja/issues/1533 and documentation still needs to be updated.
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#601
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?