This documentation is maintained by the community, it is not guaranteed to be complete or up-to-date. We always recommend users read the third-party documentation as part of the integration process to ensure the configuration matches their needs and as such we always link the documentation if available. If you find an error in this documentation please either make a GitHub Pull Request or start a GitHub Discussion.
Before You Begin
- You are required to utilize a unique client id for every client.
- The client id on this page is merely an example and you can theoretically use any alphanumeric string.
- 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:
- Authelia Root URL:
- Client ID:
- Client Secret:
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
- id: guacamole description: Apache Guacamole secret: '$plaintext$guacamole_client_secret' public: false authorization_policy: two_factor redirect_uris: - https://guacamole.example.com scopes: - openid - profile - groups - email response_types: - id_token grant_types: - implicit userinfo_signing_algorithm: none