Kasm Workspaces

Tested Versions

Before You Begin

Common Notes

  1. The OpenID Connect 1.0 client_id parameter:
    1. This must be a unique value for every client.
    2. The value used in this guide is merely for demonstration purposes and you can theoretically use nearly any alphanumeric string.
  2. The OpenID Connect 1.0 secret parameter:
    1. The value used in this guide is merely for demonstration purposes and you should absolutely not use this in production and should instead utilize the How Do I Generate Client Secrets FAQ.
    2. This string may be stored as plaintext in the Authelia configuration but this behaviour is deprecated and is not guaranteed to be supported in the future. See the Plaintext guide for more information.
  3. The Configuration example for Authelia is only a portion of the required configuration and it should be used as a guide in conjunction with the standard OpenID Connect 1.0 Configuration guide.


This example makes the following assumptions:

  • Application Root URL: https://kasm.example.com
  • Authelia Root URL: https://auth.example.com
  • Client ID: kasm
  • Client Secret: insecure_secret



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

  1. Visit Authentication
  2. Visit OpenID
  3. Set the following values:
    1. Enable Automatic User Provision if you want users to automatically be created in Kasm Workspaces.
    2. Enable Auto Login if you want automatic user login.
    3. Enable Default if you want Authelia to be the default sign-in method.
    4. Client ID: kasm
    5. Client Secret: insecure_secret
    6. Authorization URL: https://auth.example.com/api/oidc/authorization
    7. Token URL: https://auth.example.com/api/oidc/token
    8. User Info URL: https://auth.example.com/api/oidc/userinfo
    9. Scope (One Per Line): openid profile groups email
    10. User Identifier: preferred_username
Kasam Workspaces


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

    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See: https://www.authelia.com/c/oidc
      - id: kasm
        description: Kasm Workspaces
        secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: two_factor
          - https://kasm.example.com/api/oidc_callback
          - openid
          - profile
          - groups
          - email
        consent_mode: implicit
        userinfo_signing_algorithm: none

See Also