mirror of
https://github.com/plankanban/planka.git
synced 2026-02-25 03:14:50 +03:00
Feature Request: Header or env variable based authentication #161
Reference in New Issue
Block a user
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?
Originally created by @Forceu on GitHub (Jan 21, 2022).
It would be amazing if Planka supported either headers or env variables for authentication.
The use case would be SSO software running on the reverse proxy, in my case Authelia with Nginx. I can configure Nginx to set a header or env variable containing the username and one containing the user role. So if Planka checks the header and a user with that username exists, a new session is created.
It would be even better if a new user would automatically be created if the username cannot be found, but that use case would not be super important for me. I already looked through the code, unfortunately I was not able to implement the feature myself.
Thanks!
@lorenz commented on GitHub (Feb 16, 2022):
I have started working on OIDC integration in https://github.com/plankanban/planka/pull/203, would this also work for you?
@max-tet commented on GitHub (Feb 20, 2022):
I also would love to have a proxy auth feature and OIDC would not work for me.
I am running Planka behind a Traefik reverse proxy which handles all my authentication needs and can set headers on the requests it passes on. The perfect proxy auth feature for me would work like this:
admin=admin_user)proxy_auth=true)auth_header=X-Authenticated-User)X-Authenticated-Userto the authenticated username on every request.That way, user management could be mostly delegated to the reverse proxy which is extremely helpful if you have multiple apps behind the same proxy and want to take care of user management only once.
Edit: BTW, I am using Planka for this product. Since this is a single-user platform, users really should see no login screen at all, not even for SSO.
Thanks a lot!
@Forceu commented on GitHub (Feb 20, 2022):
Yes, I have a similar setup and although OIDC would already make it easier, header authentication would be even better! If I can help in any way let me know!
@prologic commented on GitHub (Jul 22, 2023):
I'd also like proxy auth via HTTP trusted header/proxies as well. I'd love to put Authelia in front of this 👌
@saadqaz1 commented on GitHub (Feb 27, 2024):
I'm using Traefik and Authelia as a OIDC provider for Planka and SSO works great but for some reason the 'OIDC_ROLES_ATTRIBUTE' config doesn't seem to work for me when I try setting it to '=admin' then creating a LLDAP group called 'admin' and adding the user.
The user just has read only access so I have to add that user to each project/board via the default admin.
@oomenit commented on GitHub (May 24, 2024):
Could you comment how you got Authelia working? I have followed the OIDC guide but Planka keeps giving me an 'unknown' error with no logging at all when trying to login with SSO.
My Authelia config:
client_name: Planka
client_secret: {KEY}
authorization_policy: two_factor
public: false
consent_mode: implicit
audience: []
scopes:
- openid
- profile
- email
userinfo_signed_response_alg: none
redirect_uris:
- https://DOMAIN/oidc-callback
and my docker-compose for Planka:
But I keep getting:
@saadqaz1 commented on GitHub (Jul 7, 2024):
This is my authelia config:
'''
clients:
- id: planka
description: Planka
secret: my_secret
#sector_identifier: ''
#public: false
'''
And my planka config:
'''
- OIDC_ISSUER=https://authelia.local
- OIDC_CLIENT_ID=planka
- OIDC_CLIENT_SECRET=my_secret
- OIDC_SCOPES=openid email profile
- OIDC_ADMIN_ROLES=admin
# - OIDC_EMAIL_ATTRIBUTE=email
# - OIDC_NAME_ATTRIBUTE=name
# - OIDC_USERNAME_ATTRIBUTE=preferred_username
- OIDC_ROLES_ATTRIBUTE=groups
# - OIDC_IGNORE_USERNAME=true
- OIDC_IGNORE_ROLES=true
# - OIDC_ENFORCED=true
'''
@rcosta-uk commented on GitHub (Nov 22, 2024):
Old post but hey, here is it:
Hi, I got myself the same error. After looking into the authelia logs I found that was needed to specify the response type config on authelia side:
https://www.authelia.com/configuration/identity-providers/openid-connect/clients/#response_types
Worked after that!
Regards
@dakky commented on GitHub (Aug 5, 2025):
did you manage to fix this issue? Login works but the user still only has read permissions
authelia database:
autheliia OIDC client config:
and in planka: