Now You Can Setup Centrify, OneLogin, Ping and Other Identity Providers with Cloudflare Access
We use Cloudflare Access to secure our own internal tools instead of a VPN. As someone that does a lot of work on the train, I can attest this is awesome (though I might be biased). You can see it in action below. Instead of having to connect to a VPN to reach our internal jira, we just login with our Google account and we are good to go:
Before today, you could setup Access if you used GSuite, Okta or Azure AD to manage your employee accounts. Today we would like to announce support for two more Identity Providers with Cloudflare Access: Centrify and OneLogin.
We launched Cloudflare Access earlier this year and have been overwhelmed by the response from our customers and community. Customers tell us they love the simplicity of setting up Access to secure applications and integrate with their existing identity provider solution. Access helps customers implement a holistic solution for both corporate and remote employees without having to use a VPN.
If you are using Centrify or OneLogin as your identity provider you can now easily integrate them with Cloudflare Access and have your team members login with their accounts to securely reach your internal tools.
Oh and one last thing, We have a new generic connector which allows you to integrate any OIDC based identity provider with Cloudflare Access. OpenID Connect (OIDC) is supported by many identity providers (some popular OIDC based Identity Providers are Ping Identity and Forgerock)
If you’re eager to get started, steps are below for configuring OneLogin, Centrify and a custom OIDC provider. Each take about 3–5 minutes. Hope you enjoy!
Steps for setting up Centrify
Login to your Centrify admin portal and click on apps.
Click on Add Web Apps and navigate to custom tab. Scroll down and click Add on OpenID Connect.
Click Yes on the Application modal to create an OpenID Connect app.
Enter an Application ID and click save.
Navigate to the trust tab and enter a strong application secret. Under the Service Provider configuration enter your application’s authentication domain as the Resource application URL. Click Add on Authorized redirect URIs and put your authentication domain/cdn-cgi/access/callback. Click Save.
Now copy your Client ID, Client Secret, OpenID Connect Issuer URL without the forward slash and Application ID from Settings tab in the Centrify dashboard and then paste them into the Cloudflare dashboard.
Steps for setting up OneLogin
Login to your Onelogin admin portal and click on custom connectors.
Click on New Connector
Name the connector and select OpenID Connect as the sign on method. In the redirect URI field, put your authentication domain/cdn-cgi/access/callback. Click Save.
Click on More Actions and select Add App to Connector.
Name the app and click save.
Navigate to the SSO tab and click on show client secret.
Now copy your Client ID and Client Secret from the Onelogin dashboard and then paste them into the Cloudflare dashboard.
Setting up a custom identity provider using OIDC
The following are the information you would need from your identity provider into the Cloudflare Dashboard.
- Client ID and Client Secret: IdPs let you create a client or an app for each custom integration. You can create one for Access and grab the client id and secret.
- Auth URL: This is the authorization_endpoint URL of your IdP.
- Token URL: This is the token_endpoint URL of your IdP.
- Certificate URL: The jwks_uri endpoint of your IdP is where you get the keys used by the IdP to sign the tokens.
All the above endpoint values can be obtained from your IdP’s OIDC discovery endpoint which is also called as the well-known URL. For example if you use Ping as your identity the URL would be <hostname>/.well-known/openid-configuration
Give your IdP connector a name of your choice by entering it in the Name field.
In your IdP’s Authorized redirect URI field, put your authentication domain/cdn-cgi/access/callback URL.
Originally published at blog.cloudflare.com on April 23, 2018.
