Apache Guacamole

Tested Versions

Before You Begin

Common Notes

  1. You are required to utilize a unique client id for every client.
  2. The client id on this page is merely an example and you can theoretically use any alphanumeric string.
  3. You should not use the client secret in this example, We strongly recommend reading the Generating Client Secrets guide instead.


This example makes the following assumptions:

  • Application Root URL: https://guacamole.example.com
  • Authelia Root URL: https://auth.example.com
  • Client ID: guacamole
  • Client Secret: guacamole_client_secret



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

openid-client-id: guacamole
openid-scope: openid profile groups email
openid-issuer: https://auth.example.com
openid-jwks-endpoint: https://auth.example.com/jwks.json
openid-authorization-endpoint: https://auth.example.com/api/oidc/authorization?state=1234abcedfdhf
openid-redirect-uri: https://guacamole.example.com
openid-username-claim-type: preferred_username
openid-groups-claim-type: groups


The following YAML configuration is an example Authelia client configuration for use with Apache Guacamole which will operate with the above example:

- id: guacamole
  description: Apache Guacamole
  secret: '$plaintext$guacamole_client_secret'
  public: false
  authorization_policy: two_factor
    - https://guacamole.example.com
    - openid
    - profile
    - groups
    - email
    - id_token
    - implicit
  userinfo_signing_algorithm: none

See Also