[PM-39789] fix: allow SCIM POST to create users disabled in the IdP#7891
Open
sander-adamse wants to merge 1 commit into
Open
[PM-39789] fix: allow SCIM POST to create users disabled in the IdP#7891sander-adamse wants to merge 1 commit into
sander-adamse wants to merge 1 commit into
Conversation
Collaborator
|
Thank you for your contribution! We've added this to our internal tracking system for review. Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process. |
JimmyVo16
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📔 Objective
Remove the
!model.Activecondition from the legacy InviteScimOrganizationUserAsync in PostUserCommand.cs. Previously a SCIM POST /Users withactive: falsewas rejected with a 400, so accounts disabled in the IdP (e.g. staged onboarding or intentionally inactive shared accounts) could never be created in the organization.Our provisioning process requires support for accounts that are pre-created in a disabled state (for example, users staged ahead of onboarding). These accounts need to exist in Bitwarden so they can be activated later. Additionally, the BadRequestException() makes it harder to identify real provisioning issues.
📸 Screenshots
N/A