#keycloak

8 posts · Last used Sep 29

#GetFediHired #FediHire : I'm looking for a job (EU-remote, preferably part-time). I have 12+ years of experience in security, from PhD to security engineer and security architect. I know my way around #ThreatModelling, #appsec , Hashicorp #Vault, #devsecops , #Kubernetes security, #Gatekeeper, infrastructure/#cloudsecurity, IAM/RBAC, #Keycloak and many other things. Also I'm able to pick up new things fairly quickly. I'm generally quite thorough, and good at paying attention to details (which I think is essential in security). If you need some experienced security engineer or architect, or know someone who does, let's talk!
0
1
4
0
Replying to
@dansup@mastodon.social Full agree: the Fediverse needs to become easier and more familiar to use. But that should mean open, self-hostable standards too. I would really like to see #OIDC / #OpenID Connect as a built-in option — like #Mastodon supports, or #PeerTube can gain through plugins — alongside Sign in with Apple, Google, etc. For Pixelfed, an easy .env-based configuration for a generic OIDC provider would be ideal: issuer URL, client ID, client secret, scopes, redirect URI — done. That would let instance admins use #Keycloak, #Authentik, #Zitadel, their university/work SSO, or any other compatible provider. Does #Loops have plans for generic OIDC login? And is this planned for #Pixelfed as well? Making sign-up familiar matters. Making it interoperable and self-hostable matters just as much. #OpenIDConnect #SelfHosting #Fediverse
6
4
2
0
Replying to
It's been a while since my last post and a lot has happened. Hence, a quick update. I've fully migrated from #freeipa to #kanidm by now and while this path was definitely not without (also major) problems and a lot of back and forth also with the developers, I overall don't regret the decision at all. While kanidm arguably falls behind in popularity/visibility compared to #authentik, #keycloak, etc and seemingly also has (much?) less developers, and development therefore feels slower, it scores with simplicity and by offering exactly what I need. See here for a quick comparison: https://kanidm.com/comparisons/ I have around 10 services connected to it and all is working fine (finally now). What is a bit annoying about OIDC is that not all services offer OIDC out of the box, i.e. sometimes additional plugins are needed. The other annoying thing is that OIDC implementations differ, e.g. in how group mapping are used (if at all). If you are looking for a one-stop solution that offers OIDC, SSH key provisioning and replication - don't look any further.
11
0
6
0

Achievement unlocked: SSO for the hypervisor! 🎉

My Proxmox VE is now officially using Keycloak OIDC for authentication, and the setup is fantastic:

  • Centralized Users: Managed alongside my other apps (Keycloak using my LDAP as the backend).

  • Hardware MFA: Locked down with a FIDO2 stick from @nitrokey@social.nitrokey.com

  • Unified Control: Centralized policies, logging, and RBAC across the board.

Another great improvement for my HomeLab/SelfHosting setup.

#Proxmox #Keycloak #DevOps #Auth #OpenID #Homelab #SelfHosted

22
3
11
0