When adding a server in the player, multiple requests are sent to Emby’s AuthenticateByName API, resulting in multiple API keys being generated.
Regular player only one API key, but infuse for different play request will generate different api key
This is exactly the same issue I reported before.,Infuse doesn’t use valid tokens for authentication; instead, it keeps making new login requests, which causes the session count to keep growing. Just check your Emby/Jellyfin login logic.
Right logic: Get the token on the first login, store it in the client, and use the valid token for any auth-related operations instead of repeatedly logging in to generate new tokens. Only re-login to get a new token when the current one is no longer valid.
We have checked, and Infuse sends only one authentication request on login and cold launch.
- Where and how are you seeing multiple requests/devices? A screenshot or specific example would be helpful.
- How is the Emby server and Infuse setup configured (EG server address, port, HTTPS, etc.)?
- What do the Emby server logs show when the issue occurs?
- Can you send in server and Infuse logs from the same period?
We’ve already discussed this in DMs, and I’ve pointed out where the issue lies. Even the Jellyfin thread mentioned it (constant logout and login). Other players only show single-digit sessions in their screenshots, but Infuse can have hundreds. It keeps sending requests to the AuthenticateByName API. I can’t provide logs, and honestly, I’m out of options with your dev team.
If you can PM me these logs it would be very helpful in identifying the situation(s) where this may happen.
had pm you
i had pm you, please check
use http/https capture tool to get open infuse request,I get some new discover that open infuse will send AuthenticateByName( this api include user account and pwd) request to emby server and response access token, but ever open infuse will repeat above option and get new access token, I search emby doc get the emby access token is lifetime valid, so cause session more and more, use other player we discover them request is always use only one access token, I do not know infuse why not obey correct use rule
only use emby of infuse have show 669 session Count, your dev infuse is so crazy
As soon as Infuse opens, it logs back in to get a new token. Bro, please follow the dev guidelines.
Open once, add once, it’s too crazy
Thanks for sharing the details. We’re looking into this specific situation. It does not seem to happen with most other Emby servers.
Bro, I’ve already explained this clearly in my private message. Currently, Infuse invokes the AuthenticateByName API every time it is opened. AuthenticateByName is the login API; it needs to be called only once to obtain an access token and store it on the client. Subsequent authorization operations should use this access token. Your current approach involves calling AuthenticateByName on every launch of Infuse, rather than utilizing the access token obtained during the initial login. The Emby documentation explicitly states that the access token becomes invalid only when a logout is performed or when a 401 error occurs, at which point re-login is required. I have described the issue in detail and provided evidence. Do you still not understand?
Please review the code logic for opening the Infuse application to determine whether it requests authentication via AuthenticateUponOpen.
会话数量 : 681
this is latest session quantity
A set of improvements in this area have been added in todays 8.5.7 update. 