How to properly organize websocket survivability?

Question

Information Security

The task is this, there is a front and a backend that communicate via a web socket. It is necessary to make authorization for some users. Now, when entering the site, a websocket connection immediately opens, if the user wants to log in, then it turns out that he needs to break the connection, request a login / password via http and open a new connection for him, which will already have rights?