osec Login Protection: Rate limits and IP / domain rules for osec Auth
Sign-in rules that know about emails and codes, not just IPs: per-email and per-IP code limits per hour, wrong-code limits, IP allow and deny lists, allowed email domains and disposable-email blocking. No DNS move.
What it does
- Code requests per IP and per email, per hour
- Failed-code limits per IP
- IP and CIDR allow / deny lists
- Only allow your company's email domains
What goes in, what comes out
- What goes in
- Rules you set per project: sign-in codes per IP and per email per hour, wrong codes per IP per hour, IP allow and deny lists, allowed email domains, and whether to block disposable addresses.
- What comes out
- osec Auth refuses a code request or a sign-in that breaks a rule and shows the visitor a plain message. Blocked attempts are listed in the console.
- Example
- Allowed email domains set to yourcompany.com: a sign-in from a gmail.com address is refused before any code is sent.
- Limits
- Works only with osec Auth sign-in. Not counted against the request quota. A changed rule applies within 30 seconds. If the rule check cannot be reached, sign-in keeps working.
How to set it up
Rules osec Auth applies before sending or accepting a sign-in code, and before finishing a Google or Apple sign-in. Not metered.
- Console → Login protection → pick your project.
- Set limits: codes per IP and per email per hour, wrong codes per IP per hour.
- Optional: IP deny list, IP allow list (e.g. office only), allowed email domains, block disposable emails.
- Save. Rules apply within 30 seconds. Blocked attempts show in the same page.
Good to know
- IP lists, allowed email domains and disposable-email blocking also apply to Google and Apple sign-in. Code limits apply to email codes.
- Blocked users see a clear message in the sign-in dialog (e.g. "Too many sign-in codes requested. Try again in an hour.").
- If the rule check is ever unavailable, sign-in keeps working (fail open).