<p>I am building an application gateway in Golang, communicating with various different technologies (primarily .NET at present, but this will broaden on rollout) via Websockets (the Gorilla implementation)</p>
<p>I am fairly new to the Golang ecosystem, and am hoping to get some honest recommendations for the authentication / authorisation of socket connections.</p>
<p>I have tried googling around, but would like to hear the active opinions of the community.</p>
<hr/>**评论：**<br/><br/>a_t-2: <pre><p>You don't need websocket for that, authenticate with http, and since the user is authenticated before upgrading to a websocket connection you don't need to anything else to authorize the user.</p></pre>lagerdalek: <pre><p>Thanks, that’s true now I think about it</p></pre>
