glauth VS kanidm

I would go with ldap server such as https://github.com/glauth/glauth. As for apps directly configure with ldap or add a proxy such as https://github.com/authelia/authelia

I was thinking about something along the lines of https://github.com/glauth/glauth - but that tool doesn't support the exact use case, I think. Are there any alternatives?

Another project, glauth: https://github.com/glauth/glauth. it's written in Go and has a declarative config--you can define users and groups in yaml. Makes it really easy to do HA etc.

Check this: https://github.com/kanidm/kanidm/ Maybe not production ready, but looks very promising

Kanidm is a identity management platform with a ldap compatible interface, sso and more. It's still young, but the author works on the 389 ldap server at suse, so knows how to build a secure ldap alternative :)

Here is the OAuth/OIDC issue: https://github.com/kanidm/kanidm/issues/278

They are talking here: https://github.com/kanidm/kanidm/pull/485 about being an IdP with support for OIDC, so once that is implemented you could probably federate to Keycloak (or any other compliant IdP).

Might be worth filing an issue, I'm sure they'd love the feedback.

Kanidm: A simple, secure and fast identity management platform\ (22 comments)

Kanidm, it might not sound as fun or exciting but this sound engineering driven by exceptional people. Similarly, concread.

saml-rs, creating a SAML IdP in rust, kind of spun out of trying to do it for Kanidm.

And now they employ one of the lead 389 Directory Server developers (now the default in SUSE instead of OpenLDAP which is is still available but is going to be depreciated). The same person is also the lead developer of Kandim, a new beta IDM that looks really promising (but is likely quite some time from being ready for enterprise production).