Skip to main content

Sign-in and limits

Sign-in

  • The login is compared case-insensitively: User_Freedom and user_freedom are the same login. A login cannot contain spaces.
  • The password is set by a platform administrator. A new password takes effect within a minute; during that time the old one may still be accepted.
  • One response to any sign-in failure. A wrong password, an unknown login, a disabled account, empty user or pass — all respond with {"type":"error", "data":"Authentication failed"}. Platform engineers see the exact reason in the logs.

Temporary lockout

Two wrong passwords within one second, or many wrong passwords in a row, lock the login for a while: first for a minute, then longer, but no more than 15 minutes. The lockout is never permanent: if scheduled requests keep going out with an old password, sign-in recovers on its own once the password is fixed.

Rate limits

Above the limit, the response is {"type":"error", "data":"Too many requests, try again later"} (added by the platform). Rejected requests do not extend the window. The per-login limit also counts unknown logins.
If all clients come through a single forwarding that does not pass their addresses, the per-address limit becomes shared by everyone. Engineers can see this in the logs.

Repeating the same request

The same request body (ignoring user and pass) sent again within 10 minutes gets the stored response with the same IDs, and no rows are added. See Repeated requests for details.