mirror of
https://github.com/pomerium/pomerium.git
synced 2025-08-03 16:59:22 +02:00
docs: fix typo (#566)
This commit is contained in:
parent
799d1ad162
commit
297b0fd6c7
3 changed files with 3 additions and 3 deletions
|
@ -37,7 +37,7 @@ As mentioned above, Pomerium supports mixing and matching configuration. For exa
|
|||
|
||||
## Run
|
||||
|
||||
Finally, source the the configuration `env` file and run pomerium specifying the `config.yaml` .
|
||||
Finally, source the configuration `env` file and run pomerium specifying the `config.yaml` .
|
||||
|
||||
```bash
|
||||
source ./env
|
||||
|
|
|
@ -64,7 +64,7 @@ The application interacting with Pomerium must manage the following workflow. Co
|
|||
1. The script or application opens a browser or redirects the user to the returned login page.
|
||||
1. The user completes the identity providers login flow.
|
||||
1. The identity provider makes a callback to pomerium's authenticate service (e.g. `authenticate.corp.domain.example`) .
|
||||
1. Pomerium's authenticate service creates a user session and redirect token, then redirects back to the the managed endpoint (e.g. `httpbin.corp.domain.example`)
|
||||
1. Pomerium's authenticate service creates a user session and redirect token, then redirects back to the managed endpoint (e.g. `httpbin.corp.domain.example`)
|
||||
1. Pomerium's proxy service and makes a callback request to the original `redirect_uri` with the user session and refresh token as arguments.
|
||||
1. The script or application is responsible for handling that http callback request, and securely handling the callback session (`pomerium_jwt`) and refresh token (`pomerium_refresh_token`) queryparams.
|
||||
1. The script or application can now make any requests as normal, by setting the `Authorization: Pomerium ${pomerium_jwt}` header.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue