mirror of
https://github.com/pomerium/pomerium.git
synced 2025-08-01 16:01:26 +02:00
Docs: Update JWT Verification Guide (#2746)
* WIP update * init mutual auth topic page * WIP * update JWT verification guide * s/Java/Json/g * remove Mutual Auth topic page and references The new page will be reviewed and added as a separate PR * fix JSON capitalization throughout * copy edit to jwt-verification.md Co-authored-by: cmo-pomerium <91488121+cmo-pomerium@users.noreply.github.com>
This commit is contained in:
parent
a8b76bd623
commit
f016981194
6 changed files with 200 additions and 190 deletions
|
@ -5,7 +5,7 @@ description: This article describes how to to get a user's identity with Pomeriu
|
|||
|
||||
# Getting the user's identity
|
||||
|
||||
This article describes how to retrieve a user's identity from a pomerium managed application. Pomerium uses JSON Web Tokens (JWT) to attest that a given request was handled by Pomerium's authorizer service.
|
||||
This article describes how to retrieve a user's identity from a pomerium managed application. Pomerium uses JSON web tokens (JWT) to attest that a given request was handled by Pomerium's authorizer service.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
|
@ -14,7 +14,7 @@ In enterprise environments where multiple services protected by Pomerium communi
|
|||
|
||||
## Abstract
|
||||
|
||||
When a User communicates with a service downstream of Pomerium, the service can identify that user by the `X-Pomerium-JWT-Assertion` header, added by Pomerium, which provides as a value a Java Web Token (**JWT**) identifying the user.
|
||||
When a User communicates with a service downstream of Pomerium, the service can identify that user by the `X-Pomerium-JWT-Assertion` header, added by Pomerium, which provides as a value a JSON web token (**JWT**) identifying the user.
|
||||
|
||||
Should that service need to communicate with another Pomerium-protected service to construct the response, that connection should be authorized through Pomerium with a [Service Account](/enterprise/concepts.md#service-accounts). Service accounts should be provided to Pomerium from the first service as a bearer token header, i.e. `Authorization: Bearer Pomerium-${service_acount_jwt}`. This header is how the secondary service authenticates the machine-to-machine interaction.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue