Files
authelia/docs/content/integration/openid-connect/clients/jellyseerr/index.md
T
2026-09-09 11:35:34 +00:00

4.4 KiB
Raw Blame History

title, description, summary, date, draft, images, weight, toc, aliases, support, seo
title description summary date draft images weight toc aliases support seo
Jellyseerr Integrating Jellyseerr with the Authelia OpenID Connect 1.0 Provider. 2025-06-08T10:42:30+00:00 false
620 true
/integration/openid-connect/jellyseerr/
level versions integration
community true true
title description canonical noindex
Jellyseerr | OpenID Connect 1.0 | Integration Step-by-step guide to configuring Jellyseerr with OpenID Connect 1.0 for secure SSO. Enhance your login flow using Authelia’s modern identity management. false

Tested Versions

{{% oidc-common %}}

Assumptions

This example makes the following assumptions:

  • Application Root URL: https://jellyseerr.{{< sitevar name="domain" nojs="example.com" >}}/
  • Authelia Root URL: https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/
  • Client ID: jellyseerr
  • Client Secret: insecure_secret

Some of the values presented in this guide can automatically be replaced with documentation variables.

{{< sitevar-preferences >}}

Authelia

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

identity_providers:
  oidc:
    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See: https://www.authelia.com/c/oidc
    clients:
      - client_id: 'jellyseerr'
        client_name: 'Jellyseerr'
        client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: 'two_factor'
        require_pkce: false
        pkce_challenge_method: ''
        redirect_uris:
          - 'https://jellyseerr.{{< sitevar name="domain" nojs="example.com" >}}/login?provider=authelia&callback=true'
        scopes:
          - 'openid'
          - 'email'
          - 'profile'
          - 'groups'
        response_types:
          - 'code'
        grant_types:
          - 'authorization_code'
        access_token_signed_response_alg: 'none'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_post'

Application

The following instructions will guide you through the UI-based configuration of Jellyseerr to utilize Authelia as an OpenID Connect 1.0 Provider.

  1. Go to the Settings page from the left-hand navigation in Jellyseerr.
  2. Under the Users tab, you should see "Enable OpenID Connect Sign-In", if you are on the correct branch. Add OpenID Connect Provider
  3. Click the Cog icon next to "Enable OpenID Connect Sign-In" then select Add OpenID Connect Provider.
  4. Configure the following options:
    • Provider Name: Authelia
    • Logo: https://www.authelia.com/images/branding/logo-cropped.png
    • Issuer URL: https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}
    • Client ID: jellyseerr
    • Client Secret: insecure_secret
    • Scopes: openid profile email groups
    • Allow New Users: Checked Example of provider settings
  5. All other options may remain unchecked or unconfigured.
  6. Click Save Changes.
  7. Click Close to return to the Settings page.
  8. Ensure the Enable OpenID Connect Sign-In option is checked
  9. Scroll down to the bottom of the page and click Save Changes.
  10. To log in visit https://jellyseerr.{{< sitevar name="domain" nojs="example.com" >}}/api/v1/auth/oidc/login/authelia.

A login button is also added to the Jellyseerr login page, which will redirect to Authelia for authentication.

Login Page

See Also