Entra ID as identity provider via SAML federation. XML-based assertion flow — no client secret.
Loading...
SAML uses a redirect-based flow. Cloudflare (the Service Provider / SP) redirects the user to Entra ID (the Identity Provider / IdP) with a SAML AuthnRequest. Entra authenticates the user and posts a signed XML assertion back to Cloudflare's Assertion Consumer Service (ACS) URL. Cloudflare validates the signature using the IdP's certificate, applies the Access policy, and issues its JWT cookie.
Unlike OIDC, there is no client secret. Trust is established through X.509 certificate signing. The SP and IdP exchange metadata to configure each other.
Cloudflare Access — SAML Demo, select "Integrate any other application you don't find in the gallery"https://<your-team>.cloudflareaccess.com/cdn-cgi/access/callbackhttps://<your-team>.cloudflareaccess.com/cdn-cgi/access/callbackCloudflare Access requires the user's email address. Ensure the claim emailaddress maps to user.mail or user.userprincipalname.
Download the Certificate (Base64) from the SAML Signing Certificate section. You will upload this to Cloudflare.
Copy the Login URL and Azure AD Identifier (Entity ID) from the Set up section.
email → http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddressbarbicancloud.co.uk/saml/* (path) or saml.barbicancloud.co.uk (subdomain)barbicancloud.co.uk/saml/saml.barbicancloud.co.uk