Tested Versions

Before You Begin

Important Reading

This section contains important elements that you should carefully consider before configuration of an OpenID Connect 1.0 Registered Client.

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 readability and demonstration purposes and you should not use this value in production and should instead utilize the How do I generate a client identifier or client secret? FAQ. We recommend 64 random characters but you can use any arbitrary value that meets the other criteria.
    3. This must only contain RFC3986 Unreserved Characters.
    4. This must be no more than 100 characters in length.
  2. The OpenID Connect 1.0 client_secret parameter:
    1. The value used in this guide is merely for demonstration purposes and you should absolutely not use this value in production and should instead utilize the How do I generate a client identifier or client secret? 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. When the secret is stored in hashed form in the Authelia configuration (heavily recommended), the cost of hashing can, if too great, cause timeouts for clients. See the Tuning the work factors guide for more information.
  3. The configuration example for Authelia:
    1. Only contains an example configuration for the client registration and you MUST also configure the required elements from the OpenID Connect 1.0 Provider Configuration guide.
    2. Only contains a small portion of all of the available options for a registered client and users may wish to configure portions that are not part of this guide or configure them differently, as such it’s important to both familiarize yourself with the other options available and the effect of each of the options configured in this section by looking at the OpenID Connect 1.0 Clients Configuration guide.


This example makes the following assumptions:

  • Application Root URL:
  • Authelia Root URL:
  • Client ID: jellyfin
  • Client Secret: insecure_secret



The following YAML configuration is an example Authelia client configuration for use with Jellyfin which will operate with the application example:

    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See:
      - client_id: 'jellyfin'
        client_name: 'Jellyfin'
        client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: 'two_factor'
        require_pkce: true
        pkce_challenge_method: 'S256'
          - ''
          - 'openid'
          - 'profile'
          - 'groups'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_post'


Important Note: This configuration assumes Jellyfin administrators are part of the jellyfin-admins group, and Jellyfin users are part of the jellyfin-users group. Depending on your specific group configuration, you will have to adapt the AdminRoles and Roles nodes respectively. Alternatively you may elect to create a new authorization policy in provider authorization policies then utilize that policy as the client authorization policy.

To configure Jellyfin to utilize Authelia as an OpenID Connect 1.0 Provider:

  1. Visit the Jellyfin Administration Dashboard.

  2. Visit the Plugins section.

  3. Visit the Repositories tab.

  4. Click the + to add a repository.

  5. Enter the following details:

    1. Repository Name: Jellyfin SSO
    2. Repository URL:
  6. Click Save.

  7. Click Ok to confirm the repository installation.

  8. Visit the Catalog tab.

  9. Select SSO Authentication from the Authentication section.

  10. Click Install.

  11. Click Ok to confirm the plugin installation.

  12. Once installed restart Jellyfin.

  13. Complete steps 1 and 2 again.

  14. Click the SSO-Auth plugin.

  15. Add a provider with the following settings:

    1. Name of the OID Provider: Authelia

    2. OID Endpoint:

    3. OpenID Client ID: jellyfin

    4. OID Secret: insecure_secret

    5. Enabled: Checked

    6. Enable Authorization by Plugin: Checked

    7. Enable All Folders: Checked

    8. Roles: jellyfin-users

    9. Admin Roles: jellyfin-admins

    10. Role Claim: groups

    11. Request Additional Scopes: groups

    12. Set default username claim: preferred_username

  16. All other options may remain unchecked or unconfigured.

  17. Click Save.

Alternatively you can utilize the following configuration XML:

<?xml version="1.0" encoding="utf-8"?>
<PluginConfiguration xmlns:xsi="" xmlns:xsd="">
  <SamlConfigs />
          <EnabledFolders />
          <LiveTvRoles />
          <LiveTvManagementRoles />
          <FolderRoleMappings />

See Also