News for hackers. Stuff that matters.

A comment on Keycloak: Open-source identity and access management. Parent comment

Re:Keycloak: Open-source identity and access management by snuxoll on Tuesday April 14, 2020 @09:16PM (#22873434)
Setting up OpenLDAP or 389ds and integrating Keycloak with it is hardly rocket science - no need to reinvent the wheel.
[ Parent | on HN ]
Re:Keycloak: Open-source identity and access management by vetinari on Wednesday April 15, 2020 @07:25AM (#22876510)
Setting it up with FreeIPA (which contains 389ds) is a matter of filling up a single form in Keycloak admin.

That includes SPNEGO (passwordless auth in browser) for those, who are enrolled into domain or have Kerberos tickets.

[ Parent | on HN ]
Re:Keycloak: Open-source identity and access management by kiney on Wednesday April 15, 2020 @10:20AM (#22877994)
FreeIPA has it's own set of problems. One being basically unrunnable in containers because of weird systemd stuff
[ Parent | on HN ]
Re:Keycloak: Open-source identity and access management by vetinari on Wednesday April 15, 2020 @10:25AM (#22878060)
FreeIPA is not supported in containers, because it is integration of a bunch of services that need to be on the same machine and each of them has its own idea where to keep state.

It has nothing to do with systemd, despite what systemd-phobes think.

[ Parent | on HN ]
Re:Keycloak: Open-source identity and access management by doublerabbit on Friday April 17, 2020 @06:08AM (#22897659)
And is somewhat broken and bodged with FreeBSD.
[ Parent | on HN ]