Commons typos in Auth0 Setup
- Audience mix up attack
- Business critical information in
user_metadata
- Link to unverified emails
id_token
as bearer token (this is not about privacy only)
- weak token validation (RS256, nonce, state, c_hash, etc)
- Confidential clients for public applications
- Neglect API rate limits
- Neglect application settings hygiene (grants, local callback urls, allowed connections, allowed origins, etc)
- Neglect tenant housekeeping (mfa admin, tagging, security settings, legacy flags, dynamic registration, enable application/connection)
- Lack of proper logout
- Open to DDoS by calling management API in public API or login process (mostly due to custom HRD or mutable fields in metadata)
- Naive
user_id
design (e.g. sequential) or unnecessarily mastering it
- Open sign-ups for protected databases
- Tokens transport in query parameters (opens the door for replay attacks)
- Canonical domain name as issuer (open the door for WAF bypass)
- Modelling single business as multiple audiences or put versioning in audience