Skip to content

fix(admin)!: make kid required for create_jwt#42

Merged
johnpmitsch merged 1 commit into
mainfrom
fix/jwt-kid-required
Jun 23, 2026
Merged

fix(admin)!: make kid required for create_jwt#42
johnpmitsch merged 1 commit into
mainfrom
fix/jwt-kid-required

Conversation

@johnpmitsch

Copy link
Copy Markdown
Collaborator

Makes kid a required parameter for POST /endpoints/:id/security/jwts (create_jwt). Previously it was optional in the SDK's typed surface, so callers omitting it only found out via a server-side rejection. Now they get a compile/type error.

Changes across all four bindings:

  • core: CreateJwtRequest.kid is now String (was Option<String>)
  • python: signature is create_jwt(id, kid, public_key=None, name=None)
  • node: generated CreateJwtRequest.kid is now required (kid: string)
  • ruby: validated via hash_require_string; .rbs updated to kid: String
  • docs + Rust/Ruby examples updated; all four READMEs now list kid as required

Breaking change

This tightens the type for callers not already passing kid. Warrants a minor bump and a !-marked changeset.

Verification

cargo check, just lint, just node-build, just python-build, just ruby-build, just test all pass (211 tests, 0 failures).

The kid (key identifier) is required when creating a JWT on an endpoint
via POST /endpoints/:id/security/jwts. Reflect that in the typed surface
so callers get a compile/type error instead of a server-side rejection.

- core: CreateJwtRequest.kid is now String (was Option<String>)
- python: create_jwt(id, kid, public_key=None, name=None)
- node: CreateJwtRequest.kid is now required
- ruby: kid validated via hash_require_string; rbs updated
@johnpmitsch johnpmitsch merged commit 803bfa3 into main Jun 23, 2026
4 checks passed
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.

2 participants