2022-06-15 07:51:47 +00:00
---
title: "Cloudflare Zero Trust"
2022-07-01 03:07:02 +00:00
description: "Integrating Cloudflare Zero Trust with the Authelia OpenID Connect Provider."
2022-06-15 07:51:47 +00:00
lead: ""
2022-06-28 05:27:14 +00:00
date: 2022-06-15T17:51:47+10:00
2022-06-15 07:51:47 +00:00
draft: false
images: []
menu:
integration:
parent: "openid-connect"
weight: 620
toc: true
community: true
---
## Tested Versions
* [Authelia]
* [v4.35.6 ](https://github.com/authelia/authelia/releases/tag/v4.35.6 )
## Before You Begin
2023-02-02 01:30:06 +00:00
{{% oidc-common %}}
2022-10-20 04:42:22 +00:00
2022-10-20 04:27:09 +00:00
### Assumptions
2022-06-15 07:51:47 +00:00
This example makes the following assumptions:
* __Cloudflare Team Name:__ `example-team`
* __Authelia Root URL:__ `https://auth.example.com`
* __Client ID:__ `cloudflare`
2023-02-02 01:30:06 +00:00
* __Client Secret:__ `insecure_secret`
2022-06-15 07:51:47 +00:00
2022-10-15 21:37:31 +00:00
*__Important Note:__ [Cloudflare Zero Trust] does not properly URL encode the secret per [RFC6749 Appendix B] at the
time this article was last modified (noted at the bottom). This means you'll either have to use only alphanumeric
characters for the secret or URL encode the secret yourself.*
2022-10-15 21:30:02 +00:00
2023-02-02 01:30:06 +00:00
[RFC6749 Appendix B]: https://datatracker.ietf.org/doc/html/rfc6749#appendix-B
2022-08-31 11:03:21 +00:00
2022-06-15 07:51:47 +00:00
## Configuration
### Application
2022-08-31 11:03:21 +00:00
*__Important Note:__ It is a requirement that the Authelia URL's can be requested by Cloudflare's servers. This usually
means that the URL's are accessible to foreign clients on the internet. There may be a way to configure this without
accessibility to foreign clients on the internet on Cloudflare's end but this is beyond the scope of this document.*
2023-01-25 23:59:18 +00:00
To configure [Cloudflare Zero Trust] to utilize Authelia as an [OpenID Connect 1.0] Provider:
2022-06-15 07:51:47 +00:00
1. Visit the [Cloudflare Zero Trust Dashboard ](https://dash.teams.cloudflare.com )
2. Visit `Settings`
3. Visit `Authentication`
4. Under `Login nethods` select `Add new`
5. Select `OpenID Connect`
2022-07-01 03:07:02 +00:00
6. Set the following values:
2022-06-15 07:51:47 +00:00
1. Name: `Authelia`
2. App ID: `cloudflare`
2023-02-02 01:30:06 +00:00
3. Client Secret: `insecure_secret`
2022-06-15 07:51:47 +00:00
4. Auth URL: `https://auth.example.com/api/oidc/authorization`
5. Token URL: `https://auth.example.com/api/oidc/token`
6. Certificate URL: `https://auth.example.com/jwks.json`
2022-08-31 11:03:21 +00:00
7. Enable `Proof Key for Code Exchange (PKCE)`
8. Add the following OIDC Claims: `preferred_username` , `mail`
2022-06-15 07:51:47 +00:00
7. Click Save
### Authelia
The following YAML configuration is an example __Authelia__
[client configuration ](../../../configuration/identity-providers/open-id-connect.md#clients ) for use with [Cloudflare]
which will operate with the above example:
```yaml
2023-04-02 03:12:01 +00:00
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- id: cloudflare
description: Cloudflare ZeroTrust
secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
authorization_policy: two_factor
redirect_uris:
- https://example-team.cloudflareaccess.com/cdn-cgi/access/callback
scopes:
- openid
- profile
- email
userinfo_signing_algorithm: none
2022-06-15 07:51:47 +00:00
```
## See Also
* [Cloudflare Zero Trust Generic OIDC Documentation ](https://developers.cloudflare.com/cloudflare-one/identity/idp-integration/generic-oidc/ )
[Authelia]: https://www.authelia.com
[Cloudflare]: https://www.cloudflare.com/
[Cloudflare Zero Trust]: https://www.cloudflare.com/products/zero-trust/
2023-01-25 23:59:18 +00:00
[OpenID Connect 1.0]: ../../openid-connect/introduction.md