-
Notifications
You must be signed in to change notification settings - Fork 334
Add multi-ingress domains to SCIM IdPs #4778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
5b2b73f
to
559a318
Compare
We have to set some constraints on this field that wouldn't fit in the general case.
This should be up-to-date with what the migrations create.
6a8da79
to
c2457d1
Compare
Hey @fisx 👋 May I ask you to review this? This PR touches sensitive areas and you surely have most knowledge/context here... |
in later lookups, at most one IdP can be configured per multi-ingress domain. | ||
If multi-ingress is not configured or it's not configured for the specific | ||
domain, no `domain` field gets added to the IdP. This guards against creating | ||
multiple IdPs and then assigning them to multi-ingress domains. Thus, users who |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you mean "guards against a team having no multi-ingress, but several idps that are only distinguished by domain (because domain is part of the database key)?
we do allow several idps per team, though, right? except there is some complication with scim and saml, and associating the two for one ipd, not sure what the current implementation status there is.
not sure this makes sense, but i'll leave it as a note to self so i can clarify later.
Ticket: https://wearezeta.atlassian.net/browse/WPB-20052
Checklist
changelog.d