OIDC Sign-In for Omada Controller with a SAML Bridge

Sat, 24 Oct 2026 18:30:00 +0200

I wanted to use an existing OIDC identity provider for Omada Controller sign-in. Omada expects SAML for this flow, so I forked Omada SAML to OIDC Bridge and adapted it for homelab deployments, with a focus on reducing its memory footprint. In my homelab, I saw the container’s memory use drop from about 260 MB to around 70 MB. That’s an observation from my setup, not a universal benchmark.

The bridge uses SATOSA for the OIDC-to-SAML flow and a small reverse proxy for Omada’s Assertion Consumer Service (ACS). It can work with providers such as Pocket ID and Authelia.

Identity on duchnovsky.com

OIDC Sign-In for Omada Controller with a SAML Bridge