Skip to content

[PM-39789] fix: allow SCIM POST to create users disabled in the IdP#7891

Open
sander-adamse wants to merge 1 commit into
bitwarden:mainfrom
sander-adamse:fix/scim-allow-inactive-user-provisioning
Open

[PM-39789] fix: allow SCIM POST to create users disabled in the IdP#7891
sander-adamse wants to merge 1 commit into
bitwarden:mainfrom
sander-adamse:fix/scim-allow-inactive-user-provisioning

Conversation

@sander-adamse

@sander-adamse sander-adamse commented Jun 30, 2026

Copy link
Copy Markdown

📔 Objective

Remove the !model.Active condition from the legacy InviteScimOrganizationUserAsync in PostUserCommand.cs. Previously a SCIM POST /Users with active: false was 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

@sander-adamse sander-adamse requested a review from a team as a code owner June 30, 2026 09:56
@sander-adamse sander-adamse requested a review from JimmyVo16 June 30, 2026 09:56
@bitwarden-bot

Copy link
Copy Markdown
Collaborator

Thank you for your contribution! We've added this to our internal tracking system for review.
ID: PM-39789
Link: https://bitwarden.atlassian.net/browse/PM-39789

Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process.

@bitwarden-bot bitwarden-bot changed the title fix: allow SCIM POST to create users disabled in the IdP [PM-39789] fix: allow SCIM POST to create users disabled in the IdP Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants