Client private key authentication #7

Open
opened 2026-03-07 05:17:04 +00:00 by eelke · 0 comments
Owner

For confidential flow the client can also be configured to prove it's identity by sending a signed JWT. In this case the service only needs the public key so the secret only will exist in one place.

For confidential flow the client can also be configured to prove it's identity by sending a signed JWT. In this case the service only needs the public key so the secret only will exist in one place.
eelke added the
enhancement
label 2026-03-07 05:17:04 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: eelke/IdentityShroud#7
No description provided.