4.3 KiB
title | description | summary | date | draft | images | weight | toc | support | seo | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cloudflare Zero Trust | Integrating Cloudflare Zero Trust with the Authelia OpenID Connect 1.0 Provider. | 2022-06-15T17:51:47+10:00 | false | 620 | true |
|
|
Tested Versions
{{% oidc-common %}}
Assumptions
This example makes the following assumptions:
- Cloudflare Team Name:
example-team
- Authelia Root URL:
https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/
- Client ID:
cloudflare
- Client Secret:
insecure_secret
Some of the values presented in this guide can automatically be replaced with documentation variables.
{{< sitevar-preferences >}}
{{< callout context="caution" title="Important Note" icon="outline/alert-triangle" >}} 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. {{< /callout >}}
Configuration
Authelia
The following YAML configuration is an example Authelia client configuration for use with Cloudflare which will operate with the application example:
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- client_id: 'cloudflare'
client_name: 'Cloudflare ZeroTrust'
client_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_signed_response_alg: 'none'
Application
{{< callout context="caution" title="Important Note" icon="outline/alert-triangle" >}} It is a requirement that the Authelia URL's can be requested by Cloudflare's servers. This usually means that the URLs 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. {{< /callout >}}
To configure Cloudflare Zero Trust to utilize Authelia as an OpenID Connect 1.0 Provider:
- Visit the Cloudflare Zero Trust Dashboard
- Visit
Settings
- Visit
Authentication
- Under
Login methods
selectAdd new
- Select
OpenID Connect
- Set the following values:
- Name:
Authelia
- App ID:
cloudflare
- Client Secret:
insecure_secret
- Auth URL:
https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/api/oidc/authorization
- Token URL:
https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/api/oidc/token
- Certificate URL:
https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/jwks.json
- Enable
Proof Key for Code Exchange (PKCE)
- Add the following OIDC Claims:
preferred_username
,mail
- Name:
- Click Save