Meta API: forward transport info from proxy to router

[oberstet]

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:

[oberstet]

Once a proxy frontend session from a connecting client is established, some details of the already accepted frontend session and transport are stored

crossbar/crossbar/worker/proxy.py

Line 198 in 8521972

self._custom_authextra = {

and later picked up again

crossbar/crossbar/worker/proxy.py

Line 564 in 8521972

msg = message.Welcome(self._session_id,

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

crossbar/crossbar/worker/proxy.py

Line 327 in 8521972

# forward authentication credentials of the connecting client

---

once we have that, we can use the frontend session and transport details then known to the router worker

crossbar/crossbar/router/router.py

Line 75 in 8521972

self._session_id_to_session = {}

holding the service session for the realm in the WAMP meta API

crossbar/crossbar/router/service.py

Line 230 in 8521972

@wamp.register('wamp.session.get')

[oberstet]

this is now fixed, that is, the connecting transport details are forwarded - but not yet picked up at the router end #2006