starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

[PR #15559] [MERGED] Disable legacy authorization methods by default #14344

New Issue
Closed
opened 2026-02-07 07:28:18 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 07:28:18 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/15559
Author: @nielsvanvelzen
Created: 11/18/2025
Status: ✅ Merged
Merged: 11/27/2025
Merged by: @nielsvanvelzen

Base: master ← Head: disable-legacy-auth

📝 Commits (2)

  • 196c243 Disable legacy authorization methods by default
  • 67c67df Use async migration

📊 Changes

2 files changed (+33 additions, -1 deletions)

View changed files

➕ Jellyfin.Server/Migrations/Routines/DisableLegacyAuthorization.cs (+32 -0)
📝 MediaBrowser.Model/Configuration/ServerConfiguration.cs (+1 -1)

📄 Description

This is part 2 of 3 for the removal of legacy authorization method. Previously we added an configuration options that is disabled by default in #13306 which released with 10.11. This PR will change the EnableLegacyAuthorization option to false for all installs, allowing a user to (temporarily) keep using the legacy method if they use an client that is not updated yet.

Getting this into 10.12 unstable builds early so clients that haven't migrated yet will know in time.

We'll remove this configuration option (and the authorization methods) in a future release, likely 10.13.

Changes

  • Disable legacy authorization methods by default

Issues

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/15559 **Author:** [@nielsvanvelzen](https://github.com/nielsvanvelzen) **Created:** 11/18/2025 **Status:** ✅ Merged **Merged:** 11/27/2025 **Merged by:** [@nielsvanvelzen](https://github.com/nielsvanvelzen) **Base:** `master` ← **Head:** `disable-legacy-auth` --- ### 📝 Commits (2) - [`196c243`](https://github.com/jellyfin/jellyfin/commit/196c243a7d53d06a5fe492942442d48bba9727c4) Disable legacy authorization methods by default - [`67c67df`](https://github.com/jellyfin/jellyfin/commit/67c67df5077af5c90242fc5fc36373b2ae6f2c91) Use async migration ### 📊 Changes **2 files changed** (+33 additions, -1 deletions) <details> <summary>View changed files</summary> ➕ `Jellyfin.Server/Migrations/Routines/DisableLegacyAuthorization.cs` (+32 -0) 📝 `MediaBrowser.Model/Configuration/ServerConfiguration.cs` (+1 -1) </details> ### 📄 Description This is part 2 of 3 for the removal of legacy authorization method. Previously we added an configuration options that is disabled by default in #13306 which released with 10.11. This PR will change the EnableLegacyAuthorization option to false for all installs, allowing a user to (temporarily) keep using the legacy method if they use an client that is not updated yet. Getting this into 10.12 unstable builds early so clients that haven't migrated yet will know in time. We'll remove this configuration option (and the authorization methods) in a future release, likely 10.13. **Changes** - Disable legacy authorization methods by default **Issues** <!-- Tag any issues that this PR solves here. ex. Fixes # --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 07:28:18 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#14344
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?