080bb594b2
- To better support having multiple downstream providers configured, the authorize endpoint will share a CSRF cookie between all downstream providers' authorize endpoints. The first time a user's browser hits the authorize endpoint of any downstream provider, that endpoint will set the cookie. Then if the user starts an authorize flow with that same downstream provider or with any other downstream provider which shares the same domain name (i.e. differentiated by issuer path), then the same cookie will be submitted and respected. - Just in case we are sharing the domain name with some other app, we sign the value of any new CSRF cookie and check the signature when we receive the cookie. This wasn't strictly necessary since we probably won't share a domain name with other apps, but it wasn't hard to add this cookie signing. Signed-off-by: Ryan Richard <richardry@vmware.com> |
||
|---|---|---|
| .. | ||
| certauthority | ||
| client | ||
| concierge | ||
| config | ||
| constable | ||
| controller | ||
| controllerlib | ||
| controllermanager | ||
| downward | ||
| dynamiccert | ||
| here | ||
| httputil | ||
| mocks | ||
| multierror | ||
| oidc | ||
| oidcclient | ||
| plog | ||
| registry/credentialrequest | ||
| testutil | ||