ContextQMD
Back to Authelia

Terrakube

docs/content/integration/openid-connect/clients/terrakube/index.md

4.39.193.2 KB
Original Source

Tested Versions

{{% oidc-common %}}

Assumptions

This example makes the following assumptions:

  • Application Root URL: https://terrakube.{{< sitevar name="domain" nojs="example.com" >}}/
    • This option determines the redirect URI in the format of https://terrakube.{{< sitevar name="domain" nojs="example.com" >}}/login. This means if you change this value, you need to update the redirect URI.
  • Authelia Root URL: https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/
  • Client ID: terrakube
  • Client Secret: insecure_secret

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

{{< sitevar-preferences >}}

Configuration

Authelia

The following YAML configuration is an example Authelia client configuration for use with Terrakube which will operate with the application example:

yaml
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: 'terrakube'
        client_name: 'Terrakube'
        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://terrakube.{{< sitevar name="domain" nojs="example.com" >}}/dex/callback'
        scopes:
          - 'openid'
          - 'email'
          - 'profile'
        response_types:
          - 'code'
        grant_types:
          - 'authorization_code'
        access_token_signed_response_alg: 'none'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_post'

Application

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

Configuration File

{{< callout context="tip" title="Did you know?" icon="outline/rocket" >}} The configuration file below is the Dex configuration for Terrakube. {{< /callout >}}

To configure Terrakube to utilize Authelia as an OpenID Connect 1.0 Provider, use the following configuration:

yaml
connectors:
  - type: oidc
    id: TerrakubeClient
    name: TerrakubeClient
    config:
      issuer: "https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}"
      clientID: "terrakube"
      clientSecret: "insecure_secret"
      redirectURI: "https://terrakube.{{< sitevar name="domain" nojs="example.com" >}}/dex/callback"
      insecureEnableGroups: true

See Also