Apache Guacamole

Tested Versions

Before You Begin

You are required to utilize a unique client id and a unique and random client secret for all OpenID Connect relying parties. You should not use the client secret in this example, you should randomly generate one yourself. You may also choose to utilize a different client id, it’s completely up to you.

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 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
  secret: guacamole_client_secret
  public: false
  authorization_policy: two_factor
    - openid
    - profile
    - groups
    - email
    - https://guacamole.example.com
    - id_token
    - implicit
  userinfo_signing_algorithm: none

See Also