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

OpenID documentation wrong / providers not working #2207

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

Originally created by @regnerisch on GitHub (Apr 3, 2025).

Description

I created a config.yml like described in the documentation:

auth:
  openid:
    enabled: true
    providers:
      pocketid:
        name: "Pocket ID"
        authurl: ".../authorize"
        clientid: "..."
        clientsecret: "..."

Also the code seems to support that (valid) yaml. But I always get an internal server error (https://my-domain.com/api/v1/info)

If I change the providers to an array instead of an object (which is not documented but shown in many examples)
I do not get an error, but the openid_providers inside the API-info endpoint is an empty array. Which is also wrong. I am not able to sign up or login with my OIDC provider as the frontend just shows the normal login/sign up page.

auth:
  openid:
    enabled: true
    providers:
      - name: "Pocket ID"
         authurl: ".../authorize"
         clientid: "..."
         clientsecret: "..."

I'm pretty sure this is not intended. This need to be fixed inside the code and the documentation must be updated too. It sould be an array or an object and should be consistant between the config documentation and examples.

Vikunja Version

0.24.6

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @regnerisch on GitHub (Apr 3, 2025). ### Description I created a config.yml like described in the documentation: ```yaml auth: openid: enabled: true providers: pocketid: name: "Pocket ID" authurl: ".../authorize" clientid: "..." clientsecret: "..." ``` Also the code seems to support that (valid) yaml. But I always get an internal server error (https://my-domain.com/api/v1/info) If I change the providers to an array instead of an object (which is not documented but shown in many examples) I do not get an error, but the `openid_providers` inside the API-info endpoint is an empty array. Which is also wrong. I am not able to sign up or login with my OIDC provider as the frontend just shows the normal login/sign up page. ```yaml auth: openid: enabled: true providers: - name: "Pocket ID" authurl: ".../authorize" clientid: "..." clientsecret: "..." ``` I'm pretty sure this is not intended. This need to be fixed inside the code and the documentation must be updated too. It sould be an array or an object and should be consistant between the config documentation and examples. ### Vikunja Version 0.24.6 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:57:25 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 3, 2025):

The syntax in your very first example is the one in current unstable builds and the next release. The 0.24.6 release uses your second example.

If there is an error while accessing the info endpoint, there should be something in the logs.

@kolaente commented on GitHub (Apr 3, 2025): The syntax in your very first example is the one in current unstable builds and the next release. The 0.24.6 release uses your second example. If there is an error while accessing the info endpoint, there should be something in the logs.
GiteaMirror commented 2026-03-22 13:57:25 -05:00
Author
Owner
Copy Link

@regnerisch commented on GitHub (Apr 4, 2025):

But when I use the syntax of version 0.24.6, why vikunja does not show the provider inside the info endpoint nor on sign up or sign in?

It's a little bit confusing that the documentation is for the unstable builds, maybe you consider versioning the documentation as well.

@regnerisch commented on GitHub (Apr 4, 2025): But when I use the syntax of version 0.24.6, why vikunja does not show the provider inside the info endpoint nor on sign up or sign in? It's a little bit confusing that the documentation is for the unstable builds, maybe you consider versioning the documentation as well.
GiteaMirror commented 2026-03-22 13:57:25 -05:00
Author
Owner
Copy Link

@regnerisch commented on GitHub (Apr 4, 2025):

Okay I see what I did wrong. The auth.openid.providers.<provider>.authurl is NOT the authorization url of the provider, its just the url/domain where the provider is hosted as vikunja determin the right authorization url from the provider via the OIDC discovery url. Fixing that url, fixed the hole problem.

@regnerisch commented on GitHub (Apr 4, 2025): Okay I see what I did wrong. The `auth.openid.providers.<provider>.authurl` is NOT the authorization url of the provider, its just the url/domain where the provider is hosted as vikunja determin the right authorization url from the provider via the OIDC discovery url. Fixing that url, fixed the hole problem.
GiteaMirror commented 2026-03-22 13:57:26 -05:00
Author
Owner
Copy Link

@blalor commented on GitHub (Jun 4, 2025):

I had this same issue. Thanks for detailing what you did, @regnerisch.

@blalor commented on GitHub (Jun 4, 2025): I had this same issue. Thanks for detailing what you did, @regnerisch.
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#2207
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?