What's the use case for TLS parameters?

[Victor Diez]

I'm migrating my WAMP application from http to https, and all autobahn connections to wss. I'm using Wamp.rt router, passing a https server with its certificate and key. Right now I don't use any TLS config in my autobahn clients, and don't really understand the point for the TLS parameters in the connection to the router (here).

Why do we need those TLS parameters if the connection to the router is already on a secure channel?

[Tobias Oberstein]

Hi,

I assume you refer to AutobahnJS.

AutobahnJS supports running in browser (HTML5) contexts, and running under NodeJS.

When running under NodeJS it is often desirable to have more control over the TLS connection that is established as part of a WSS connection.

When running in browsers, there is no need (and no way) of modifying TLS - the browser takes care of everything.

Cheers,

/Tobias

Am 03.12.18 um 13:26 schrieb Victor Diez:

I'm migrating my WAMP application from http to https, and all autobahn connections to wss. I'm using Wamp.rt router, passing a https server with its certificate and key. Right now I don't use any TLS config in my autobahn clients, and don't really understand the point for the TLS parameters in the connection to the router (here).

Why do we need those TLS parameters if the connection to the router is already on a secure channel?

--
You received this message because you are subscribed to the Google Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autobahnws+...@googlegroups.com.
To post to this group, send email to autob...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autobahnws/e528efa8-9391-4a11-9415-f31908e1c4ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tobias Oberstein]

Hi,

I assume you refer to AutobahnJS.

AutobahnJS supports running in browser (HTML5) contexts, and running under NodeJS.

When running under NodeJS it is often desirable to have more control over the TLS connection that is established as part of a WSS connection.

When running in browsers, there is no need (and no way) of modifying TLS - the browser takes care of everything.

Cheers,

/Tobias

Am 03.12.18 um 13:26 schrieb Victor Diez:

I'm migrating my WAMP application from http to https, and all autobahn connections to wss. I'm using Wamp.rt router, passing a https server with its certificate and key. Right now I don't use any TLS config in my autobahn clients, and don't really understand the point for the TLS parameters in the connection to the router (here).

Why do we need those TLS parameters if the connection to the router is already on a secure channel?

[Victor Diez]

Hello Tobias,

thanks for answering. Yes indeed I was referring to AutobahnJS, clients both in NodeJS and browser.

I ended up in this page, and assumed it was more related to client authentication on top of the already encrypted transport layer.

I understand then it's not something I have to deal with in principle when migrating to wss.

Cheers,

Victor