Skip to content

Commit

Permalink
specify that private key should be associated with public
Browse files Browse the repository at this point in the history
  • Loading branch information
nprimak committed Aug 8, 2024
1 parent bb1db67 commit 13bf86e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _pages/oidc/token.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ sidenav:

---
{% capture client_assertion %}
A [JWT](https://jwt.io/){:class="usa-link--external"} signed with the client’s private key (minimum length of 2048 bits) using the RS256 algorithm and containing the following claims:
A [JWT](https://jwt.io/){:class="usa-link--external"} signed with the client’s private key (minimum length of 2048 bits) associated with the public key uploaded to your application configuration within the Dashboard. The JWT should use the RS256 algorithm and containing the following claims:
- **iss** (string) — The issuer, which must be the `client_id`.
- **sub** (string) — The subject, which must also be the `client_id`.
- **aud** (string) — The audience, which should be (or, in the case of multiple audience values, include) the URL of the token endpoint, for example: `https://idp.int.identitysandbox.gov/api/openid_connect/token`
Expand Down

0 comments on commit 13bf86e

Please sign in to comment.