Repository navigation
Extend User Profile validation to partialImport and realm import (mirrors #50123 fix for clients) #52704
Closed
marcele-santos
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'd like to work on #52310 - user import (partialImport, full realm import, and boot-time
--import-realm) skips User Profile validation entirely, so imported users can violate constraints that the Admin API would reject with a 400.Same class of bug as #50123, fixed in #51725 for clients. Planning to follow the same pattern for users: validate at the end of both import paths, using a new
UserProfileContextvalue since none of the existing ones fit an import.Before implementing, wanted to confirm a few things:
Will add coverage in
PartialImportUserTest,mirroringPartialImportClientTest#testIllegalSchemeBaseUrlPartialImport, once there's a steer on these.Used an AI assistant to trace the code paths and draft this write-up - the read on the codebase is checked against the actual files linked above, but the design call on these questions is mine to make.
All reactions