1.5.2.0 causes spinning wheel and "CustomAuthentication was forbidden" errors on 10.11.0

[pashdown]

Connecting to Debian 13 install of Jellyfin 10.11.0, I was getting a load of 'AuthenticationScheme: "CustomAuthentication" was forbidden' errors and infinite spinning wheels until I disabled the InfuseSync plugin. With all the improvements in Jellyfin database speed and caching, is this plugin necessary anymore?

[timdesrochers]

This is an issue I just encountered and seems to be specific to non-admin accounts attempting to index/connect to Jellyfin in Library mode. Disabling the InfuseSync plugin resolved the issue for now. This has not been an issue when authenticating as an admin.

[20:01:34] [INF] [13] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.

Versions:

• Jellyfin 10.11.3
• Infuse Pro (AppleTV) 8.3.5 (5459)
• InfuseSync 1.5.2.0

[marcoraddatz]

This is an issue I just encountered and seems to be specific to non-admin accounts attempting to index/connect to Jellyfin in Library mode. Disabling the InfuseSync plugin resolved the issue for now. This has not been an issue when authenticating as an admin.

[20:01:34] [INF] [13] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.

Versions:

• Jellyfin 10.11.3
• Infuse Pro (AppleTV) 8.3.5 (5459)
• InfuseSync 1.5.2.0

That info is gold! I finally can access the lib again via Infuse. Xmas for the kids is safe 🎅

Thanks!