socket-io-client | Client app for debug socket.Io servers | Socket library

If you already have an authenticated session via http in Express, then a socket.io connection is really JUST another http connection (it actually starts with an http connection and is then converted to the webSocket protocol (with a socket.io layer on top). So, if you're willing to trust the session for the next http request from that client, then it is no different to trust the session for an incoming socket.io connection from that same client. They are the same thing.

Where it might be useful to auth a socket.io connection from scratch would be when you don't already have an authenticated http page that the socket.io connection comes from, either because the socket.io connection is its own API and own service, perhaps even on a separate host so there is no "other" auth to rely on.

Is there a need to use both approaches for authentication if you are already sharing sessions with express.

No. You can just use the express session you already have in order to now that the socket.io connection comes from the same client.

Does it add any security advantage?

Only if there's some reason you want to require auth on every new request and not rely on a session cookie at all, even for http requests. Or, if there is no session cookie because the socket.io connection goes to a different host.

It is working for me now.

I deleted bower_components, added "blockUI": "malsup/blockui", in bower.json, and ran bower install again, before running

ember server --proxy http://localhost:16000

Ref: https://github.com/bower/bower/issues/2517#issuecomment-395717660

It is very simple actually. In socketIoClient.h you have a define like so:

#define SOCKETIOCLIENT_DEBUG(...) Serial.print(__VA_ARGS__);

You can change it to:

#define SOCKETIOCLIENT_DEBUG(...) do{} while(0);

or simply:

#define SOCKETIOCLIENT_DEBUG(...)

That should rid you of the debug messages but I reckon that esp8266 by itself prints some debug messages to UART too at some special events like connecting or disconnecting to an AP. You may need to follow this from espressif's API reference:

"os_install_putc1((void *)uart1_write_char) in uart_init will set os_printf to be output from UART 1, otherwise, os_printf default output from UART 0."

os_printf is used as default printing function by the OS as well as many applications. Arduino's Serial lib should use uart0 directly and not os_printf so doing the above would only rid you of the messages the OS produces.