mirror of
https://github.com/koel/koel.git
synced 2026-04-26 09:15:59 +03:00
[GH-ISSUE #1814] [FR]: SSO Generic Provider #1004
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#1004
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @robin9991 on GitHub (Aug 22, 2024).
Original GitHub issue: https://github.com/koel/koel/issues/1814
Originally assigned to: @phanan on GitHub.
Description
Hi,
I searched weeks till i came across here. Would it be hard to implement a generic sso provider (e.g. to use with Authentik)? As it should work simmilar to the Google Oauth. Further this seems "easier" and more secure than the Header Auth, also to implement.
Additional information
Would also be interested in testing this as this is the only thing lacking a proper deployment in my env.
@Heknon commented on GitHub (Aug 30, 2024):
We are also looking for either SSO or LDAP for user management/creation
@jojom4n commented on GitHub (Jun 12, 2025):
Any update on this feature? It's the only one thing preventing me from switching to Koel so far. I know I could use a forward auth proxy to my custom self-hosted OIDC provider and I actually use it for other daemons, but I could not use mobile app if I did so and should use common browser to browse my collection
@phanan commented on GitHub (Jun 13, 2025):
I'm willing to add this into Koel, but my knowledge is limited. If you folks could explain more (e.g., how it should work, how to set up a dev/test environment etc.) I'd much appreciate.
@jojom4n commented on GitHub (Jun 19, 2025):
To be honest, I don't know how either, I suppose one could use an external library like Oauthlib, but I'm an hobbyist developer and never implemented something like that.
Alternatively, would you be able to implement an API key system, so that Koel gives user an API key to insert into the app to connect to own server without using username and/or password? This way, one could use a forward auth proxy like Tinyauth to have SSO, while being able to connect by mobile app through the API key.
@Itrimel commented on GitHub (Nov 17, 2025):
I would also be interested to have the option to use my already configured SSO provider (Authelia) to be able to manage login to Koel : right now I'm using the proxy authentication, but this doesn't work really well with the mobile app.
I was interested to see a PR to implement Authelia as a provider (#2104), but I do agree with the comment that it makes more sense to implement a more generic solution to be able to fit into more workflows. There doesn't seem to be a generic option in the Laravel Socialite Providers, but I found this third-party repo https://github.com/Kovah/laravel-socialite-oidc implementing a generic OpenId provider : maybe this can be a good start/reference for doing this ?