Logs flooded with "AuthenticationScheme: CustomAuthentication was forbidden" messages

[ebkalderon]

After logging out of the administrator user and into a non-admin account and viewing a few trailers, I start seeing the Jellyfin logs flooded with these AuthenticationScheme: CustomAuthentication was forbidden messages, with new lines appearing roughly once per second after an initial rapid burst (as seen below)

Jan 04 22:56:13 pythagoras jellyfin[356110]: [22:56:13] [INF] [24] Emby.Server.Implementations.Session.SessionManager: Creating new access token for user afa9dc12-0710-42a3-9acb-7704d80ff0f1
Jan 04 22:56:13 pythagoras jellyfin[356110]: [22:56:13] [INF] [37] Emby.Server.Implementations.HttpServer.WebSocketManager: WS fe80::d3af:79d7:989a:1eaa%2 request
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [30] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [32] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [13] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [27] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [36] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [36] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [32] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [36] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [10] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:56:18 pythagoras jellyfin[356110]: [22:56:18] [INF] [27] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
<snip>
Jan 04 22:59:22 pythagoras jellyfin[356110]: [22:59:22] [INF] [25] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:59:23 pythagoras jellyfin[356110]: [22:59:23] [INF] [8] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:59:24 pythagoras jellyfin[356110]: [22:59:24] [INF] [38] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:59:26 pythagoras jellyfin[356110]: [22:59:26] [INF] [38] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
Jan 04 22:59:27 pythagoras jellyfin[356110]: [22:59:27] [INF] [17] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was forbidden.
<continued ad infinitum>

Restarting the server only makes the onslaught of log messages stop for a short time, until the plugin gets used a few times and then it comes back again. It seems that fully uninstalling the jellyfin-plugin-tmdb plugin fixes the issue, and reinstalling it makes it come back (disabling the plugin doesn't seem to help, anecdotally).

[ebkalderon]

As nice as this plugin is, I've uninstalled this plugin for now to avoid the log spam it seemingly produces. Will reinstall whenever it can be fixed!

[ebkalderon]

Hmm, it seems this still happens quite a bit even after uninstallation. Didn't see it before first installing this plugin though, AFAIK. Might just leave this ticket open in case someone else runs into this issue as well and wants to chime in.

[crobibero]

I would be very surprised if this plugin caused the log lines as it doesn't make any requests to it's own server. More likely an issue with the web client since that can flood the api

[ebkalderon]

You're probably right. Hope this serves as another data point to figuring out the proper fix for this issue nonetheless, wherever it lies.