Skip to content

fix(user): accept password/hashed password fields in create user#738

Open
dorsha wants to merge 1 commit into
mainfrom
shuni/task-20260611184619
Open

fix(user): accept password/hashed password fields in create user#738
dorsha wants to merge 1 commit into
mainfrom
shuni/task-20260611184619

Conversation

@dorsha

@dorsha dorsha commented Jun 11, 2026

Copy link
Copy Markdown
Member

Fixes descope/etc#16186

View workflow run

Done. Here's what I changed:

lib/management/types.ts — Added password, hashedPassword, and seed fields to the UserOptions interface. Since create, createTestUser, update, and invite all spread UserOptions into the request body, these fields now flow through to the API automatically.

lib/management/user.test.ts — Added a test verifying that create correctly passes password, hashedPassword, and seed in the request body when using the options-style API.

The fix is minimal because the infrastructure already existed — UserPasswordHashed types were defined, batch operations already used them, and all single-user functions used the spread operator on UserOptions. The only gap was the interface definition.


Created by Shuni 🐕

…tions

The API supports passing password/hashedPassword/seed when creating a user,
but the SDK's UserOptions interface was missing these fields. This adds them
so create, createTestUser, update, and invite all support password fields.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant