Core 12.8.7
Your IP rules now apply to the web sign-up form and to the web API's sign-in and sign-up.
Security
- Your IP rules now apply when someone signs up on the sign-up form, with Allow public registration on, as they already did to signing in. Before, someone on a network address your rules refuse could create an account there and be signed in, and was sent the verification email. The form is now checked against your global rules before the account is created, because the account doesn't exist yet. A refused address sees Access denied from your network address. Please contact your administrator. under the email field, as on the Sign-In screen. No account is created and no email is sent. Someone on an allowed address signs up as before. See How IP access control works.
- For developers:
POST /api/andv1/ web/ login POST /api/now follow your IP rules too. They issued a web token without checking them. The sign-in is checked before the password, against the account's own rules, then its roles', then the global ones, with the super-admin break-glass, exactly like the Sign-In screen. An email address that doesn't belong to an account gets the global rules. Sign-up is checked against the global rules before the account is created, after the Allow public registration check. A refusal answersv1/ web/ register 403witherror.codeUNAUTHORIZEDand Access denied from your network address. Please contact your administrator. It issues no token, creates no account, and doesn't say whether the email address is already registered. The web token still isn't accepted by the other/api/v1/web/…endpoints. See Authenticate API requests.