I have seen many examples for extendeding the `CreateConnectionId` for the signalR hub class such as these:

<http://www.kevgriffin.com/maintaining-signalr-connectionids-across-page-instances/>

[Storing User On Login then Pushing Data On Demand](https://stackoverflow.com/questions/8130132/storing-user-on-login-then-pushing-data-on-demand)

but does changing each user's connection\_id to his UserId (keep in mind I am using the the standard asp membership provider out of the box) pose a security threat? I could see how it would be great to do this so I wouldn't have to keep an internal mapping from users to connection\_id's but also thought it could have a security threat if I store it in a cookie on a user's browser.