This only makes sense if users are allowed to
login-on-connect so srvx doesn't see users with
authenticated trusts before they have a chance to identify.
Otherwise, srvx would simply see an unauthenticated user
over the default limit and enforce the clone limit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1273
This only makes sense if users are allowed to
login-on-connect so srvx doesn't see users with
authenticated trusts before they have a chance to identify.
Otherwise, srvx would simply see an unauthenticated user
over the default limit and enforce the clone limit.