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
When a client connects to a proxy frontend worker, the client will be authenticated at the frontend proxy, after which a backend connection to a backend router worker is established. That latter backend connection is using its own authentication ("xyz-proxy").
The backend router worker will currently only remember the session and transport information associated with the proxy->router backend connection, not session and transport details of the original incoming frontend connection.
But we need (also) the latter for the WAMP meta API!
Here is an example of above, with the location marked where we need to forward the frontend session and transport information when establishing the backend connection:
The text was updated successfully, but these errors were encountered:
however, we should forward that info and the transport details of the frontend session in authextra when joining the respective realm on the backend connection to a router worker
When a client connects to a proxy frontend worker, the client will be authenticated at the frontend proxy, after which a backend connection to a backend router worker is established. That latter backend connection is using its own authentication ("xyz-proxy").
The backend router worker will currently only remember the session and transport information associated with the proxy->router backend connection, not session and transport details of the original incoming frontend connection.
But we need (also) the latter for the WAMP meta API!
Here is an example of above, with the location marked where we need to forward the frontend session and transport information when establishing the backend connection:
The text was updated successfully, but these errors were encountered: