2.3 KiB
2.3 KiB
title | description | lead | date | draft | images | menu | integration | parent | weight | toc | community |
---|---|---|---|---|---|---|---|---|---|---|---|
Apache Guacamole | Integrating Apache Guacamole with the Authelia OpenID Connect Provider. | 2022-07-13T03:42:47+10:00 | false | openid-connect | 620 | true | true |
Tested Versions
- Authelia
- Apache Guacamole
- UNKNOWN
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
Configuration
Application
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
Authelia
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
scopes:
- openid
- profile
- groups
- email
redirect_uris:
- https://guacamole.example.com
response_types:
- id_token
grant_types:
- implicit
userinfo_signing_algorithm: none