Feature-Request: max connections for user jwts

[wutkemtt]

We have a feature request for enabling a max connection restriction on user jwts. A few weeks ago we struggled with some misbehaving clients, creating ever new connections when they "detected" a lost connection to the server. So it took only a few seconds and the connection limit of that server was reached, preventing new clients and disconnected clients from getting (re-)connected. Setting a higher limit to the server will not work as these clients will create connections until the limit is reached. If it is possible to restrict the clients in the user jwt to a defined number of max connections they will only be able to create new connections to that limit. This will lower the risk for all other clients not being able to get a connection and for the whole distributed application, as only a single service will not able to communicate.

[aricart]

@wutkemtt in order to implement this we need support from the server. Currently, max connections are implemented but are associated with an account. If you assign users to different accounts, you can implement limits that are more fine-grained. I am going to reference this on the server-side.

[mehulpoddar]

Any update on this issue? We too need user-level max connection restrictions to protect our other users from being denied service.