Skip to content

Conversation

supersven
Copy link
Contributor

@supersven supersven commented Sep 17, 2025

Ticket: https://wearezeta.atlassian.net/browse/WPB-20052

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

@supersven supersven force-pushed the sventennie/scim-idp-with-domain branch from 5b2b73f to 559a318 Compare September 17, 2025 13:20
@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Sep 17, 2025
@supersven supersven changed the title Sventennie/SCIM idp with domain Add multi-ingress domains to SCIM IdPs Sep 17, 2025
@supersven supersven force-pushed the sventennie/scim-idp-with-domain branch from 6a8da79 to c2457d1 Compare September 19, 2025 06:35
@supersven supersven marked this pull request as ready for review September 19, 2025 06:36
@supersven supersven requested review from a team as code owners September 19, 2025 06:36
@supersven supersven requested a review from a team as a code owner September 19, 2025 06:36
@supersven supersven requested a review from fisx September 19, 2025 06:36
@supersven
Copy link
Contributor Author

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
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants