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

[GH-ISSUE #1533] OIDC setup guide wrong or some bug related to it #6433

New Issue
Closed
opened 2026-04-20 17:02:03 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 17:02:03 -05:00
Owner
Copy Link

Originally created by @nsmith31415 on GitHub (Sep 22, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1533

Description

I followed the OIDC setup guide, but I'm not getting a "connect with OIDC"/"connect with authelia" option at all. As far as I can tell it doesn't even recognize that authelia exists.

My config files are as follows:
Vikunja:
auth: local: enabled: false oidc: enabled: true redirecturl: 'https://tasks.domain/auth/openid/' providers: - name: 'Authelia' authurl: 'https://auth.domain' clientid: 'vikunja' clientsecret: '<secret digest>' scope: 'openid profile email'
Authelia
`

  • client_id: 'vikunja'
    client_name: 'Vikunja'
    client_secret: ''
    public: false
    authorization_policy: 'one_factor'
    require_pkce: false
    pkce_challenge_method: ''
    redirect_uris:
    - 'https://tasks.domain/auth/openid/authelia'
    scopes:
    - 'openid'
    - 'profile'
    - 'email'
    response_types:
    - 'code'
    grant_types:
    - 'authorization_code'
    access_token_signed_response_alg: 'none'
    userinfo_signed_response_alg: 'none'
    token_endpoint_auth_method: 'client_secret_basic'
    `

There's no log messages between the two of them, and no indication that OIDC is set up. I know the config is getting loaded properly because it does remove the local login option.

I followed the guides on Authelia's website and on Vikunja's website:
https://vikunja.io/docs/openid/
https://www.authelia.com/integration/openid-connect/clients/vikunja/

As far as I can tell I did everything to specification, yet I can't get an OIDC login option to show up, so I'm marking this as a bug. If it's not a bug and its a configuration issue I would love to be shown what I did wrong

Vikunja Version

latest

Browser and version

Firefox (latest?)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @nsmith31415 on GitHub (Sep 22, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1533 ### Description I followed the OIDC setup guide, but I'm not getting a "connect with OIDC"/"connect with authelia" option at all. As far as I can tell it doesn't even recognize that authelia exists. My config files are as follows: Vikunja: ` auth: local: enabled: false oidc: enabled: true redirecturl: 'https://tasks.domain/auth/openid/' providers: - name: 'Authelia' authurl: 'https://auth.domain' clientid: 'vikunja' clientsecret: '<secret digest>' scope: 'openid profile email' ` Authelia ` - client_id: 'vikunja' client_name: 'Vikunja' client_secret: '<secret>' public: false authorization_policy: 'one_factor' require_pkce: false pkce_challenge_method: '' redirect_uris: - 'https://tasks.domain/auth/openid/authelia' scopes: - 'openid' - 'profile' - 'email' response_types: - 'code' grant_types: - 'authorization_code' access_token_signed_response_alg: 'none' userinfo_signed_response_alg: 'none' token_endpoint_auth_method: 'client_secret_basic' ` There's no log messages between the two of them, and no indication that OIDC is set up. I know the config is getting loaded properly because it does remove the local login option. I followed the guides on Authelia's website and on Vikunja's website: https://vikunja.io/docs/openid/ https://www.authelia.com/integration/openid-connect/clients/vikunja/ As far as I can tell I did everything to specification, yet I can't get an OIDC login option to show up, so I'm marking this as a bug. If it's not a bug and its a configuration issue I would love to be shown what I did wrong ### Vikunja Version latest ### Browser and version Firefox (latest?) ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:02:05 -05:00
Author
Owner
Copy Link

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

This is not a bug - this is just an issue with documentation. It was not clear to me that I needed to use the "unstable" syntax, nor where that documentation was, until someone else pointed it out to me

<!-- gh-comment-id:3316572493 --> @nsmith31415 commented on GitHub (Sep 22, 2025): This is not a bug - this is just an issue with documentation. It was not clear to me that I needed to use the "unstable" syntax, nor where that documentation was, until someone else pointed it out to me
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#6433
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?