Files
authentik/website/integrations/media/jellyseerr/index.md
Teffen Ellis 6ed5cb5249 website/docs: Modal and wizard button labels (#21549)
* website/integrations: rename "Create with Provider" to "New Application"

The application list page now uses a split-button labeled
"New Application" instead of the old "Create with Provider" dropdown.
Update all 113 integration guides to match.

* website/docs: update flow, stage, and policy button labels

- "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons
- "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit
- "Create and bind stage" → "New Stage" / "Bind Existing Stage"
- "Create" (binding submit) → "Create Stage Binding"

* website/docs: update provider button labels

- "Create" → "New Provider" for trigger buttons
- "Create with Provider" → "New Application" in RAC docs
- "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt"
  for related entity creation

* website/docs: update directory button labels

- "Create" → "New Source" for federation/social login pages
- "Create" → "New Role", submit → "Create Role"
- "Create" → "New Invitation"
- Policy binding submit → "Create Policy Binding"

* website/docs: update endpoint device and system management button labels

- "Create" → "New Endpoint Connector", "New Enrollment Token",
  "New Device Access Group", "New Flow"
- Submit → "Create Device Access Group"
- "Create" → "New Notification Rule", "New Notification Transport"
- Binding submit → "Create Policy Binding"

* Reorganize policy documentation

* website/docs: address policy docs review feedback

* post-rebase

* website/docs: Reorganize policy documentation -- Revisions (#21601)

* apply suggestions

* Fix escaped.

* Fix whitespace.

* Update button label.

* Fix phrasing.

* Fix phrasing.

* Clean up stragglers.

* Format.

---------

Co-authored-by: Dominic R <dominic@sdko.org>
2026-04-16 17:35:38 +00:00

57 lines
2.9 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: Integrate with Jellyseerr
sidebar_label: Jellyseerr
support_level: community
---
## What is Jellyseerr
> Jellyseerr is a free and open source application for managing requests in your media library. It integrates with media servers like Jellyfin, Plex, and Emby, and services such as Sonarr and Radarr.
>
> -- https://docs.seerr.dev/
## Preparation
- `jellyseerr.company` is the FQDN of the Jellyseerr installation.
- `authentik.company` is the FQDN of the authentik installation.
## authentik configuration
To support the integration of Jellyseerr with authentik, you need to create an application/provider pair in authentik.
1. Log in to authentik as an administrator and open the authentik Admin interface.
2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard.
- **Application**: provide a descriptive name, a slug, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **Slug** value as it will be required later.
- **Choose a Provider type**: OAuth2/OpenID
- **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and any required configurations.
- Note the **Client ID** and **Client Secret** values because they will be required later.
- Set a `Strict` redirect URI to `https://jellyseerr.company/login?provider=authentik&callback=true`.
- Select any available signing key.
- **Configure Bindings** _(optional):_ you can create a [binding](https://docs.goauthentik.io/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a users **My applications** page.
3. Click **Submit** to save the new application and provider.
## Jellyseerr configuration
:::info
Jellyseerr OAuth support is currently in preview, please make sure to use the `preview-OIDC` Docker tag.
:::
1. Log in to Jellyseerr with an administrator account.
2. Navigate to **Settings** > **Users**.
3. Toggle on **Enable OpenID Connect Sign-In** and click on the cogwheel icon next to it.
4. Click **Add OpenID Connect Provider** and configure the following settings:
- **Provider Name**: `authentik`
- **Logo**: `https://authentik.company/static/dist/assets/icons/icon.svg`
- **Issuer URL**: `https://authentik.company/application/o/jellyseerr/`
- **Client ID**: Client ID from authentik
- **Client Secret**: Client Secret from authentik
- Under **Advanced Settings**:
- **Scopes**: `openid profile email groups`
- **Allow New Users**: Enabled
5. Click **Save Changes**.
## Configuration verification
To verify that authentik is correctly set up with Jellyseerr, log out of Jellyseerr and try logging back in using the authentik button. You should be redirected to authentik, and once authenticated you will be signed in to Jellyseerr.