Skip to content

fix!: deleteUser takes id, not email #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lakhansamani merged 1 commit into from
Aug 7, 2026
Merged

fix!: deleteUser takes id, not email #53

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/admin.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -358,7 +358,7 @@ export class AuthorizerAdmin {
params as unknown as Record<string, unknown>,
);

// deleteUser deletes a user (and associated OTP/verification data) by email.
// deleteUser deletes a user (and associated OTP/verification data) by id.
// DESTRUCTIVE: the user and their auth artifacts are permanently removed.
deleteUser = (
params: Types.DeleteUserRequest,
Expand Down
6 changes: 5 additions & 1 deletion src/types.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -372,8 +372,12 @@ export interface ResetPasswordRequest {
export type ResetPasswordInput = ResetPasswordRequest;

// DeleteUserRequest (admin only)
//
// BREAKING (server 2.4.0): this took `email` and now takes `id`. Email is not
// an identifier every account has — a phone-only signup has none — so an
// email-keyed delete could not reach those accounts at all.
export interface DeleteUserRequest {
email: string;
id: string;
}

// Fine-grained authorization (FGA) types — the client-facing surface of
Expand Down
Loading