Assigning user to InvalidAuthProvider until this is corrected.

[yannolerobot]

I am seeing these repeated warnings in my logs for every SSO user :

[XX:XX:XX] [WRN] [81] Jellyfin.Server.Implementations.Users.UserManager: User ### was found with invalid/missing Authentication Provider pocketid. Assigning user to InvalidAuthProvider until this is corrected

The message is repeated every 2 minutes or so.

Seems like the same issue as #309 , however the suggested fixes don't work for me.

Things I've tried :

• Unlinking the user and re-authenticating. That removes the warning for said user but only temporarily. Comes back after "some" time or a server restart.
• Closing every open sessions, re-starting the server : no difference
• Changing the default provider to "Jellyfin.Server.Implementations.Users.DefaultAuthenticationProvider" or leaving it empty

Jellyfin v10.11.5
SSO v4.0.0.3
conf. file attached

SSO.xml

[njhughes-01]

I am also getting this I have tried creating new providers
Creating new accounts
linking the accounts with self service before trying to login it seems like nothing is having an impact

[2026-01-12 21:21:29.628 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:29.628 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:29.628 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:29.947 -06:00] [INF] SSO Controller initialized
[2026-01-12 21:21:29.955 -06:00] [INF] Auth request created...
[2026-01-12 21:21:29.955 -06:00] [INF] Set default login provider to Jellyfin.Plugin.SSO_Auth.Api.SSOController
[2026-01-12 21:21:29.955 -06:00] [INF] Current/Max sessions for user "redacted": 0/0
[2026-01-12 21:21:29.955 -06:00] [INF] Creating new access token for user deaad6d0-f184-4fa5-9a86-ee08cc0e813f
[2026-01-12 21:21:29.959 -06:00] [WRN] User "redacted" was found with invalid/missing Authentication Provider "Jellyfin.Plugin.SSO_Auth.Api.SSOController". Assigning user to InvalidAuthProvider until this is corrected
[2026-01-12 21:21:30.297 -06:00] [WRN] User "redacted" was found with invalid/missing Authentication Provider "Jellyfin.Plugin.SSO_Auth.Api.SSOController". Assigning user to InvalidAuthProvider until this is corrected
[2026-01-12 21:21:30.317 -06:00] [INF] WS "10.88.88.77" request
[2026-01-12 21:21:30.328 -06:00] [WRN] User "killerherts@gmail.com" was found with invalid/missing Authentication Provider "Jellyfin.Plugin.SSO_Auth.Api.SSOController". Assigning user to InvalidAuthProvider until this is corrected
[2026-01-12 21:21:32.452 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:32.452 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:32.452 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:33.125 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:33.125 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:33.125 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:35.547 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:35.547 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:35.547 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:38.643 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:38.643 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:38.643 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:41.758 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:41.758 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:41.758 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:44.841 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:44.841 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:44.841 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:47.925 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:47.925 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:47.925 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:51.023 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:51.023 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:51.023 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:54.105 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:54.105 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:54.105 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:21:57.214 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:57.214 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:21:57.214 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:22:00.293 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:22:00.293 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:22:00.293 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:22:03.383 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:22:03.383 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:22:03.383 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:22:06.491 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:22:06.491 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:22:06.491 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2026-01-12 21:22:09.609 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:22:09.609 -06:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2026-01-12 21:22:09.609 -06:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.```

[njhughes-01]

So i was able to fix it by setting the ldap plugin as the default provider then just using authentics ldap informaiton for that looks like this might break the live tv role claim as ldap doesn't have that but i have to do more testing this does get it to stop trowing the invalid custom authitication error every min