Conversation
- Add matchesAllowedEmailDomain utility with exact and *.suffix pattern support - Update OIDC config service to use new matcher - *.infisical matches infisical.com, br.infisical.com, team.infisical.ai, etc. - Update frontend placeholder and API docs - Document wildcard support in SSO docs Closes PLATFRM-202 Co-authored-by: Cursor <cursoragent@cursor.com>
Greptile OverviewGreptile SummaryThis PR adds wildcard support for OIDC allowed email domains by introducing a shared Main concern is the new matcher’s wildcard logic: Confidence Score: 2/5
Important Files Changed
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
victorvhs017
left a comment
There was a problem hiding this comment.
Tested and it works great!
Context
OIDC SSO only supported exact domain matches for allowed email domains. Admins had to list every subdomain (e.g.
team.acme.com,eng.acme.com) individually.This change adds wildcard support so
*.acme.commatches any subdomain and*.infisicalmatchesinfisical.com,br.infisical.com,team.infisical.ai, etc.Closes PLATFRM-202
Screenshots
N/A – backend validation change; minor UI label/placeholder updates.
Steps to verify the change
*.infisical.comor*.infisicaluser@br.infisical.com)user@evil.comis rejectedType
Checklist
feat(sso): support wildcard email domains for OIDC