Envoy Gateway

Tested Versions#

• Authelia
  • v4.39.4
• Envoy Gateway
  • v1.4.1

Before You Begin#

Common Notes#

1. The OpenID Connect 1.0 client_id parameter:
   1. This must be a unique value for every client.
   2. The value used in this guide is merely for readability and demonstration purposes and you should not use this value in production and should instead utilize the How do I generate a client identifier or client secret? FAQ. We recommend 64 random characters but you can use any arbitrary value that meets the other criteria.
   3. This must only contain RFC3986 Unreserved Characters.
   4. This must be no more than 100 characters in length.
2. The OpenID Connect 1.0 client_secret parameter:
   1. The value used in this guide is merely for demonstration purposes and you should absolutely not use this value in production and should instead utilize the How do I generate a client identifier or client secret? FAQ.
   2. This string may be stored as plaintext in the Authelia configuration but this behaviour is deprecated and is not guaranteed to be supported in the future. See the Plaintext guide for more information.
   3. When the secret is stored in hashed form in the Authelia configuration (heavily recommended), the cost of hashing can, if too great, cause timeouts for clients. See the Tuning the work factors guide for more information.
3. The configuration example for Authelia:
   1. Only contains an example configuration for the client registration and you MUST also configure the required elements from the OpenID Connect 1.0 Provider Configuration guide.
   2. Only contains a small portion of all of the available options for a registered client and users may wish to configure portions that are not part of this guide or configure them differently, as such it’s important to both familiarize yourself with the other options available and the effect of each of the options configured in this section by looking at the OpenID Connect 1.0 Clients Configuration guide.

Assumptions#

This example makes the following assumptions:

• Application Root URL: https://envoy-app.example.com/
• Authelia Root URL: https://auth.example.com/
• Client ID: envoy-app
• Client Secret: insecure_secret

Some of the values presented in this guide can automatically be replaced with documentation variables.

Set Documentation Variables

Configuration#

Authelia#

The following YAML configuration is an example Authelia client configuration for use with Envoy Gateway 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: 'envoy-app'
        client_name: 'Envoy Gateway'
        client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: 'two_factor'
        require_pkce: false
        pkce_challenge_method: ''
        redirect_uris:
          - 'https://envoy-app.example.com/authelia/openid_connect/callback'
        scopes:
          - 'openid'
          - 'offline_access'
        grant_types:
          - 'authorization_code'
          - 'refresh_token'
        response_types:
          - 'code'
        access_token_signed_response_alg: 'none'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_basic'

Application#

To configure Envoy Gateway there is one method, using the Configuration File.

Configuration File#

Apply to a HTTPRoute#

To configure Envoy Gateway to utilize Authelia as an OpenID Connect 1.0 Provider for a single HTTPRoute, use the following instructions:

1. Use kubectl to create the secret:
   • kubectl create secret generic envoy-app-oidc-client-secret --from-literal=client-secret=insecure_secret
2. Apply the below manifests for the example application.

The following example HTTPRoute is a example real application just for the purposes of showcasing this. The important factors are the name value being envoy-app.

---
apiVersion: 'gateway.networking.k8s.io/v1'
kind: 'HTTPRoute'
metadata:
  name: 'envoy-app'
spec:
  parentRefs:
    - name: 'eg'
  hostnames:
    - 'envoy-app.example.com'
  rules:
    - matches:
        - path:
            type: 'PathPrefix'
            value: '/'
      backendRefs:
        - name: 'envoy-app-service-backend'
          port: 80
...

The following SecurityPolicy requires OpenID Connect 1.0 authorization for just the envoy-app HTTPRoute as described above, the important factors are the targetRefs which indicates what resource to apply this to.

---
apiVersion: 'gateway.envoyproxy.io/v1alpha1'
kind: 'SecurityPolicy'
metadata:
  name: 'envoy-app-oidc'
spec:
  targetRefs:
    - group: 'gateway.networking.k8s.io'
      kind: 'HTTPRoute'
      name: 'envoy-app'
  oidc:
    provider:
      issuer: 'https://auth.example.com'
      authorizationEndpoint: 'https://auth.example.com/api/oidc/authorization'
      tokenEndpoint: 'https://auth.example.com/api/oidc/token'
    clientID: 'app'
    clientSecret:
      name: 'envoy-app-oidc-client-secret'
    cookieDomain: 'envoy-app.example.com'
    cookieNames:
      idToken: ''
      accessToken: ''
    scopes:
      - 'openid'
      - 'offline_access'
    redirectURL: 'https://envoy-app.example.com/authelia/openid_connect/callback'
    forwardAccessToken: false
    refreshToken: true
    passThroughAuthHeader: false

Apply to an entire Gateway#

To configure Envoy Gateway to utilize Authelia as an OpenID Connect 1.0 Provider for an entire Gateway, use the following instructions:

1. Use kubectl to create the secret:

• kubectl create secret generic envoy-app-oidc-client-secret --from-literal=client-secret=insecure_secret

2. Apply the below manifests for the eg Gateway.

The following example HTTPRoute is a fake application just for the redirection behaviour.

---
apiVersion: 'gateway.networking.k8s.io/v1'
kind: 'HTTPRoute'
metadata:
  name: 'envoy-oidc'
spec:
  parentRefs:
    - name: 'eg'
  hostnames:
    - 'envoy-oidc.example.com'
  rules:
    - matches:
        - path:
            type: 'PathPrefix'
            value: '/'
...

The following SecurityPolicy requires OpenID Connect 1.0 authorization for every HTTPRoute on the eg Gateway, the important factors are the targetRefs which indicates what resource to apply this to.

---
apiVersion: 'gateway.envoyproxy.io/v1alpha1'
kind: 'SecurityPolicy'
metadata:
  name: 'envoy-app-oidc'
spec:
  targetRefs:
    - group: 'gateway.networking.k8s.io'
      kind: 'Gateway'
      name: 'eg'
  oidc:
    provider:
      issuer: 'https://auth.example.com'
      authorizationEndpoint: 'https://auth.example.com/api/oidc/authorization'
      tokenEndpoint: 'https://auth.example.com/api/oidc/token'
    clientID: 'app'
    clientSecret:
      name: 'envoy-app-oidc-client-secret'
    cookieDomain: 'envoy-app.example.com'
    cookieNames:
      idToken: ''
      accessToken: ''
    scopes:
      - 'openid'
      - 'offline_access'
    redirectURL: 'https://envoy-oidc.example.com/authelia/openid_connect/callback'
    forwardAccessToken: false
    refreshToken: true
    passThroughAuthHeader: false

See Also#

• Envoy Gateway
• OIDC Authentication Security Tasks