You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JWT authentication method is working ok in both cases - connecting directly to the engine (port 4747) and via the virtual proxy.
The issue is that every time when establishing connecting through the VP new session is created. This quite quickly can reach the max concurrent session limits (5) and block the JWT user from connecting (until the sessions are timed out).
The JWT connection logic should check if the connection should be established through VP or not and if yes then:
try to connect with session id (if session file exists)
first make request to the hub (via VP) and extract the sessionId
use the sessionId to establish connection
The text was updated successfully, but these errors were encountered:
JWT authentication method is working ok in both cases - connecting directly to the engine (port 4747) and via the virtual proxy.
The issue is that every time when establishing connecting through the VP new session is created. This quite quickly can reach the max concurrent session limits (5) and block the JWT user from connecting (until the sessions are timed out).
The JWT connection logic should check if the connection should be established through VP or not and if
yes
then:hub
(via VP) and extract the sessionIdThe text was updated successfully, but these errors were encountered: