Add multi-ingress domains to SCIM IdPs #4880
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket: https://wearezeta.atlassian.net/browse/WPB-20052
Adds support for associating SAML IdPs with multi-ingress domains. When multi-ingress is configured, each domain can have at most one IdP to enable deterministic SSO code resolution per email domain.
Key changes:
domainfield toWireIdPextra info, stored only for configured multi-ingress domainsfilterMultiIngressZHostto validate ZHost against configured domain mappingsguardMultiIngressDuplicateDomainchecks on IdP create/update to enforce one-IdP-per-domainSparIdPDomainInUseerror (409) when domain constraint violatedBehavior:
(domain, team) → IdPenforced at API levelChecklist
changelog.d✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.