mirror of
https://github.com/plankanban/planka.git
synced 2026-02-05 00:39:58 +03:00
SSO #63
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 @pkrolkgp on GitHub (Jan 12, 2021).
It would be nice if we can login to planka with sso for nextcloud/owncloud or any other app.
Also it would be nice to have groups in planka to assign instead of only users.
@nickbe commented on GitHub (Jan 12, 2021):
PLANKA is currently getting a complete user role overhaul. External auth systems are also on the list, but other more pressing basic changes are of a higher priority right now.
@NeodymiumPhish commented on GitHub (Mar 6, 2021):
I use Hedgedoc for some personal note-taking and collaboration with co-workers/friends, and I'm planning on doing similar with this. I'd love to be able to connect them both to the same auth0 application so the users are synced!!
Can't wait!
@terribleplan commented on GitHub (Jun 30, 2021):
Just my 2 cents here: it'd be great if whenever SSO happens it is done in a generic enough way so as to support whatever OIDC-compatible server you want (like Keycloak, WSO2, Auth0, etc)
@matbgn commented on GitHub (Aug 24, 2022):
Any news on this topic? Still a must to have as a user ans sysadmin ;-)
@GlitchWitch commented on GitHub (May 5, 2023):
Would love to know about this too!
@prologic commented on GitHub (Jul 23, 2023):
In order to solve for SSO, can we please prioritise #200 over OIDC support (#203) 🙏 The rationale here is that there are many Web servers and Authentication proxies that support this out-of-the-box, such as Authelia and supporting Proxy / HTTP Header Auth is far more trivial to do.
We should get this out first 👌
@lorenz commented on GitHub (Jul 23, 2023):
If you're building an application from scratch, I totally agree with you. In that case you can forego session management, login screens and such. It's also safer if your application does not need any unauthenticated access.
But generally once an application has an existing (usually password-based) login method, adding OIDC is easier as it more closely mimicks conventional password login (you start a session with an OIDC code instead of a password). Also it can be done mostly client-side. Another advantage is that mobile apps and native clients can easily implement OIDC (even with shared session support), whereas authenticating proxies are generally very hard as they lack a token format or anything the native client can manage and pass to the backend.
Also OIDC IDPs are more common than authenticating proxies and there is still no standardized way to pass information from the authenticating proxy to a backend application.
I'm not against doing authenticating proxy-style auth (and my IDP can do that as well), but I'm just presenting some arguments why authenticating proxy-style auth is not necessarily easier and/or better .
@prologic commented on GitHub (Jul 23, 2023):
I'm also not arguing that OIDC is better, but Proxy Auth is far easier to get going both operationally and code-wide (if you have the right interfaces in place)
Obviously I think OIDC/OAuth should continue to go ahead, I'm just saying, for the sake of "low hanging fruit with big impact", getting Proxy Auth going would solve SSO for me 👌
@jimz011 commented on GitHub (Sep 7, 2023):
I have been holding back on using planka for this very reason, I use Authentik to secure my applications, but I don't want to do a double auth (and I don't want to use the login provider provided by the application as those lack the security features that I want).
I honestly wouldn't really care how that it was done OIDC, oauth2, SAML, proxy header auth. Or even disable the password login entirely on the application would be a great start (since I would be the only user anyways). If this is already possible now I hope somebody can tell me how.
I think Planka is great otherwise and is probably the best KanBan board that I have tried over the past few years. It's just the user management that I really would love to see in one form or another (as mentioned above).
Personally I'd prefer SAML over proxy header auth (as headers can be intercepted), but hey at this point any form would do!
Thank you for this amazing project
@meltyshev commented on GitHub (Oct 17, 2023):
Released: v1.13.0 (release)