Be sure to read How to get debug information and open a proper issue to provide necessary logs and information.
Any issue without the logs can be automatically closed without further notice.
Issue description: Yatse is unable to authenticate to Jellyfin because the legacy/deprecated auth methods are disabled by using
<EnableLegacyAuthorization>false</EnableLegacyAuthorization>
in system.xml
Logs:
yatse: debug.log (15.4 KB)
Jellyfin: log_20260317.log (26.2 KB)
Screenshots:
Additional information:
The domain has be sanitized in the logs.
The logs are only for the failure with <EnableLegacyAuthorization>false</EnableLegacyAuthorization> when I change it to true everything works fine so I didn’t add logs of that.
Nightly and the next release (10.12) will default that option to false and the one after that (10.13) will remove the deprecated methods: [10.12] Default EnableLegacyAuthorization=false breaks Jellyseerr authentication · Issue #15962 · jellyfin/jellyfin · GitHub
Jellyfin auth methods and their deprecation status: Jellyfin API Authorization · GitHub
———————————————————————————————————————————————————————
I would like to keep the legacy/deprecated methods disabled (Yatse is the only thing that is broken for me right now with those disabled), is there any timeline for moving to a non deprecated auth method?