LG webOS app cannot authenticate when Google SSO is the only login method

[Evgenii Moon]

Hi,
I’m using Jellyfin with Google authentication as the only available login method. Regular Jellyfin username/password authentication is disabled intentionally.
This works fine in a normal web browser, but it makes the Jellyfin app on LG webOS effectively unusable.
When I try to sign in on the TV, Jellyfin needs to open the Google authentication page in a browser. However, the LG Jellyfin app does not seem to launch an external browser or provide any other way to complete the OAuth/SSO flow.
As a result, there is no way to authenticate in the Jellyfin app on the TV if Google SSO is the only enabled authentication method.
Enabling regular username/password authentication would technically work around the issue, but that is not a suitable solution in my case. I would prefer to keep Google authentication as the only login method.
It would be great if the LG/webOS client could support one of the following approaches:

• opening the authentication page in the TV browser;
  
• displaying a QR code or URL that can be opened on another device;
  
• using a device-code style authentication flow;
  
• or another mechanism that allows external SSO/OAuth authentication without requiring a built-in browser inside the Jellyfin app.
  

At the moment this limitation prevents me from using the Jellyfin LG app entirely.
Is there already a supported way to handle external authentication on webOS, or would this need to be implemented in the client?

[Serge K]

Did you try to use Use Quick Connect function?