Skip to content

[4.2.0] Correct the cnf / x5t#S256 example on the Securing APIs with Certificate Bound Access Tokens page #11805

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

Open
hisanhunais wants to merge 1 commit into
base: 4.2.0
Choose a base branch
from
Open

[4.2.0] Correct the cnf / x5t#S256 example on the Securing APIs with Certificate Bound Access Tokens page #11805

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
8 changes: 6 additions & 2 deletions ...urity/api-authentication/securing-apis-using-certificate-bound-access-tokens.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,9 +104,13 @@ Import the certificate and private key to Postman.

The token comprises of client certificate thumbprint as the cnf claim.

```json
"cnf": {
"x5t#S256": "mgw1cKxzkr7hSkCOyziXiFKobTjLwIf-7uqrLJoHufE"
}
```
"cnf", "{"x5t#S256": "9a0c3570ac7392bee14a408ecb38978852a86d38cbc087feeeeaab2c9a07b9f1"}"
```

The `x5t#S256` value is the base64url-encoded SHA-256 thumbprint of the DER-encoded client certificate, as defined in [RFC 8705](https://www.rfc-editor.org/rfc/rfc8705#name-jwt-certificate-thumbprint-).

4. Invoke the API from Postman.

Expand Down