Separate connection from authentication

In order to help find out if a token has expired when trying to connect, the implementation of latest etp specs is required.

According to the latest version of the ETP specs the authentication must be allowed to be in a separate step than the connection. The client must initiate the connection, then authorize before RequestSession. This will allow to get the proper error message when the connection fail because of expired token, and reauthenticate during an ongoing session (When we implement properly token expiration).

From a server perspective: We need to allow the connection when no authorization header is provided.

From a client perspective: Do the connection/authorization in two steps, so we can capture the proper error message,