#Nagios and #Bookstall are finally sitting behind #Authelia!

#sysadmin #oidc

Had a frustrating time trying to set up #netbird with #Authelia, and decided to give up in the end.
@bert_hubert I'm the last owl to take the side of big tech, but just saying, have you ever personally tried integrating oauth2/webauthn/OIDC/SSO into various #OpenSource web services? No? I want to wish you all the best of luck with that, as you roll out your enterprise-scale OpenSource deployments.

I think there's good reason all these big organizations with valiant intentions of escaping big tech, end up crawling back to big tech. The OpenSource SSO offerings leave something to be desired. Where is the realistic competitor to #Microsoft Entra? Would that be #KeyCloak? #Authelia?

It's much harder than you think.
I've managed to get #Forgejo integrated with #Authelia. I'm now trying to integrate #Kanboard with Authelia as well. Authelia continues to seem pretty decent, in that the error messages are more helpful. Debugging is easier, and I guarantee plenty of troubleshooting awaits those wanting to follow a similar path. It seems that #OIDC integration is still a new-fangled thing to many #OpenSource projects, and it's sort of treated in this second-class-citizen way. Like with Kanboard, OIDC functionality is in a plugin; isn't integrated with stock Kanboard. And even enabling the use of plugins whatsoever is *itself* a second-class feature in Kanboard. #infosec #DataSovereignty

@viq if you don't need all the bells and whistles of kanidm/authentik, I can highly recommend #authelia

easy to setup, nice troubleshooting logs, really lean on resources

@DigitalAutonomyUG Do you have a favorite #OpenSource Single Sign On solution? #Authelia? #Keycloak? What?
After trying #Keycloak for a while - trying to integrate it with ForgeJo for Single-Sign-On (#SSO), I wasn't really satisfied with Keycloak. Keycloak's error messages were too unhelpful. The documentation, too nebulous. I lurked in their forums a bit, but didn't really want to use Slack as some sort of depended-upon service. Whatever the Keycloak error messages said, the eventual solutions usually ended up being so disconnected with the error message, that it dawned on me that the Error messages were effectively "Red Herrings" - served only to throw me off the trail.

Keycloak had a vibe to it that I'd describe as "Enterprise Bozak". It had the *look* of professionalism - making a solid effort to *appear* attractive to higher-up management types - but it didn't really *deliver* the helpfulness I was expecting, to actually overcome technical hurdles encountered. I've set Keycloak aside for now, and I'm trying out #Authelia instead, with an LLDAP backend. They seem easier to work with, as the error messages were good so far: had more of a technical helpfulness. After several hours of tinkering, I've set up my first LLDAP/Authelia users, including registering a passkey. I'll next see if I can integrate the Authelia SSO to #ForgeJo.

#infosec #OpenSource
OpenCloud: Authelia als OIDC-Provider für SSO einrichten - codingblatt.de

OpenCloud mit Authelia als OIDC-Provider für Single-Sign-On einrichten.

Estudando opcións de SSO para self-hosting (e fardando das notas en Emacs usando org-roam)  

#emacs #org-roam #selfhosted #authelia

@viq interesting... #KaniDM is new for me. I was thinking to deploy #authelia in my #Selfhosting environment. I'll read more about it. Thanks

@homelab