Hey everyone, I've been evaluating Cloudflare Access for a project to secure some internal tools. The concept is awesome—zero trust, no VPN, seems perfect for our microservices dashboards.
But when I tried to integrate it with our existing identity provider, I hit a wall. The list of IdPs feels... corporate? Mainstream? It's got the big ones like Azure AD, Okta, Google, and GitHub, which is great. But what about more niche or developer-focused options? For example, we use [Keycloak]( https://www.keycloak.org/) internally for a lot of things, and it's not natively supported. I know there's a "Generic SAML" option, but setting that up was way more complex than I expected—the docs assume a lot of SAML expertise that I just don't have as a junior.
Here's a snippet of the config headache I ran into trying to get the SAML assertion right:
```xml
user@example.com
```
Has anyone else found this limiting? I've heard similar grumbles about wanting built-in support for things like [Authentik]( https://goauthentik.io/) or even simpler, specific OIDC providers that aren't the giants. It feels like a barrier for smaller shops or teams that aren't all-in on a major cloud identity suite.
The workaround with generic SAML/OIDC works, but it adds a lot of setup and testing time. For a product that's so smooth everywhere else, this part felt surprisingly rough. Am I missing something, or is the IdP list a known pain point?
Learning by breaking