Before you start
- The Super Administrator role on the Cloudflare account, which also opens the Cloudflare Zero Trust dashboard, and access to the Cloudflare API.
- A domain of your organization that you can verify in Cloudflare with a DNS record.
A SplitSecure identity provider, created in a threshold vault and approved by its Guardian Team. See Create an identity provider.
A second browser profile, signed in to the Web App, for the test sign-in. Start and finish the test in that same profile.
This guide makes your Cloudflare account a connected app of your SplitSecure identity provider, so a dashboard session starts only when your Guardian Team, the group of devices that together approve each proposal, approves it. You add SplitSecure as a SAML login method in Cloudflare Zero Trust, require it for dashboard single sign-on (SSO), and register Cloudflare in the Web App.
Values you exchange
| Value | Where to find it | Where to paste it |
|---|---|---|
| SplitSecure metadata (XML) | The identity provider’s SAML endpoints card, Download metadata XML | Cloudflare, Populate details with .xml file, in Add a SAML identity provider |
| Cloudflare metadata (XML) | Cloudflare, the metadata URL in Download the Cloudflare metadata | The Web App, Metadata File, in Create the connected app |
| SSO endpoint | Cloudflare, the dashboard SSO application, in Copy the SSO endpoint | The Web App, SSO Endpoint, in Create the connected app |
Collect the SplitSecure values
In the Web App
In the Web App, open Vaults, then your vault, then the identity provider. The SAML endpoints card shows three values:
- SAML IdP Entity ID
- SSO URL (HTTP-Redirect)
- SSO URL (HTTP-Post)
Under them, Download metadata XML saves the metadata file and Download Certificate offers the certificate in PEM format or DER format.
Click Download metadata XML on the card and save the file.
Add the SplitSecure identity provider to Cloudflare
In the Cloudflare dashboard
- Sign in to the Cloudflare dashboard (opens in a new tab).
- Go to Zero Trust → Integrations → Identity providers.
- Click Add an identity provider.
- Select SAML.
Required settings
| Field | Value |
|---|---|
| Name | SplitSecureThe name users see at the Cloudflare sign-in |
| Populate details with .xml file | The file from Download metadata XMLCloudflare fills the next three fields from it |
| Single sign-on URL | Filled from the metadata |
| IdP Entity ID or Issuer URL | Filled from the metadataMust equal the SAML IdP Entity ID on the card |
| Signing certificate | Filled from the metadata |
| Enable SCIM | Off |
Optional settings
| Field | Value |
|---|---|
| Sign SAML authentication request | On |
| Email attribute name | emailThe default. SplitSecure sends the email attribute |
| SAML attributes | Leave empty |
| SAML header attributes | Leave empty |
Click Save.
Turn on dashboard SSO
In the Cloudflare dashboard
Dashboard SSO sends every member whose email is in your domain to a login method you choose. See the Cloudflare dashboard SSO documentation (opens in a new tab) for the details.
- Go to Manage Account → Members, then click Settings.
- Under Single Sign-On (SSO) for all members, click Add domain.
- Enter your organization’s domain.
- Add the TXT record that Cloudflare shows to your DNS provider.
- Back in Cloudflare, click Verify.
Once the domain is enabled, every member with an email address in it signs in to the dashboard through SSO across all Cloudflare accounts. Cloudflare suggests creating an API token that can disable SSO for the domain, in case something goes wrong. We recommend you create one before you enable the domain.
Once your domain is verified, open its … menu and click Enable.
Require SplitSecure for the dashboard
In the Cloudflare dashboard
Cloudflare Access policies decide which login methods can open the dashboard. A policy combines an action (Allow, Block, Bypass, Service Auth) with Include, Exclude and Require rules. See Cloudflare Access policies (opens in a new tab).
This policy controls how every member of your domain signs in to the Cloudflare dashboard. A wrong rule can lock everyone out. Keep your current session open until Test the sign-in passes.
- Go to Zero Trust → Access controls → Applications.
- Open the application of type Dash SSO (usually named SSO App).
- Under Access policies, click Create new policy.
- In Policy rules, set an Include to Emails ending in and enter the domain you verified earlier.
- Click Add require, set it to Login Methods and select your SplitSecure SAML identity provider.
- Give the policy a name and click Save Policy.
- Delete the legacy policy that Cloudflare automatically generates when a domain is verified. It is usually named
Allow email domain <your-domain>.
Adding the Require rule to the policy Cloudflare generated has the same effect.
Each login method you select is one more way to open the dashboard.
| Selection | Effect | Recovery |
|---|---|---|
| SAML only | Every sign-in goes through SplitSecure | No fallback if misconfigured |
| One-time PIN and SAML | Users choose either method at sign-in | The email PIN stays available |
Connect Cloudflare to SplitSecure
In the Cloudflare dashboard
Your team name is under Zero Trust → Settings → Team domain. Open one of these URLs and save the XML file.
| Type | URL | When to use |
|---|---|---|
| Default | https://<team-name>.cloudflareaccess.com/cdn-cgi/access/saml-metadata | One SAML login method |
| IdP-specific | https://<team-name>.cloudflareaccess.com/cdn-cgi/access/<idp-id>/saml-metadata | Several SAML login methods, or custom SAML attribute mappings |
The <idp-id> can be found by opening your SplitSecure identity provider in Zero Trust → Integrations → Identity providers and copying the last part of the URL, or can be fetched from the Cloudflare API: List Access identity providers (opens in a new tab).
Go to Zero Trust → Access controls → Applications.
Open the application of type Dash SSO (usually named SSO App).
Copy its SSO endpoint. It has this shape:
https://<team-name>.cloudflareaccess.com/cdn-cgi/access/sso/saml/<app-id>
In the Web App
In the Web App, open Vaults, then your vault, then the identity provider. Click New Connected App and pick the service provider’s card. Name is required, and the Threshold Identity Provider field is fixed to this provider.
Click the Cloudflare (SAML2) card.
Enter a Name, for example
Cloudflare dashboard.Set the NameID. Cloudflare reads the email in the NameID and in the
emailattribute, which follows the NameID. Keep NameID format on Email Address.Keep the default NameID value, Built from each person’s email. Its NameID template is
${user.email}, which SplitSecure fills with the email of the person who signs in. To accept only one email domain, enter it in Email must end with, for example@example.com. SplitSecure then refuses anyone whose email ends otherwise.Under Metadata File, upload the Cloudflare XML file.
In SSO Endpoint, paste the SSO endpoint.
Optionally, under Advanced Options, turn on Selective notifications so members can choose who gets notified for the Guardian Team’s proposals, set the Account Sensitivity banner shown on this connected app’s proposals (None, Low, Medium, High or Critical), and enter a Description or a Reason for creation.
Click Propose connected app. The Web App opens the proposal under Requests. The members of the Guardian Team approve it on their devices, in the mobile app. When the vote passes, the connected app appears under Connected Apps.
Test the sign-in
In the Cloudflare dashboard
- Go to the Cloudflare dashboard (opens in a new tab).
- Go to Manage Account → Members.
- Click Invite members.
- Enter one or more email addresses in your domain.
- Set the scope to the account, and pick the roles, for example Super Administrator - All Privileges.
- Click Invite.
- Click the link in the invitation email you received from Cloudflare.
- Click on the button that says either Continue with SSO or Create SSO account.
- If you have multiple login methods set up in Cloudflare, you’ll be presented with the list. Select the SplitSecure SAML identity provider.
- You’ll be sent to the Web App, which opens the access form for the connected app.
- Enter the member’s address in your domain as the Email, then click Request Access.
- The members of the Guardian Team approve the sign-in on their devices, in the mobile app. When the vote passes, click Login.
Only the browser profile that clicked Request Access can show Login, and only once.
The Cloudflare dashboard opens, signed in as that member. Cloudflare asked for no password and no PIN.
In the Web App
- In the Web App, open Connected Apps, find the Cloudflare connected app and click Authenticate.
- If you have multiple login methods set up in Cloudflare, you’ll be presented with the list. Select the SplitSecure SAML identity provider.
- Cloudflare Access sends you back to the Web App, which opens the access form for the connected app.
- Enter the member’s address in your domain as the Email, then click Request Access.
- The members of the Guardian Team approve the sign-in on their devices, in the mobile app. When the vote passes, click Login.
The Cloudflare dashboard opens, signed in as that member.
Troubleshooting
| Issue | Solution |
|---|---|
| Continue with SSO does not appear | The domain is not verifiedFinish the DNS verification in Add and verify your domain |
| The sign-in fails at Cloudflare | The entity ID or certificate does not matchDownload the metadata again from the SAML endpoints card and upload it to Cloudflare |
| Cloudflare reports a certificate error | The certificate is wrong or expiredCheck Certificate Validity on the identity provider, then upload fresh metadata |
| Continue leads to the wrong Cloudflare page | SSO Endpoint is wrongCopy the endpoint again from the dashboard SSO application |
| A member cannot sign in | The member’s domain is not set up for SSOAdd and verify the member’s email domain in Cloudflare |
| Several login methods show at sign-in | Several SAML login methods existSelect the SplitSecure one, or keep only SAML in the policy |
| Everyone is locked out of the dashboard | The policy requires a login method that failsUse the session you kept open to add One-time PIN back to the policy |
External resources
- Identity providers (opens in a new tab): Supported IdP integrations overview
- Generic SAML 2.0 (opens in a new tab): SAML configuration guide
- Dashboard SSO (opens in a new tab): Cloudflare dashboard single sign-on