Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using JWT and proxy connection #22

Open
countnazgul opened this issue Jun 24, 2022 · 0 comments
Open

Using JWT and proxy connection #22

countnazgul opened this issue Jun 24, 2022 · 0 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@countnazgul
Copy link
Member

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
@countnazgul countnazgul added bug Something isn't working enhancement New feature or request labels Jun 24, 2022
@countnazgul countnazgul self-assigned this Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant