forked from openshift/openshift-docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Port 3.11 apache auth example for request header
- Loading branch information
Showing
3 changed files
with
126 additions
and
158 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
34 changes: 34 additions & 0 deletions
34
modules/identity-provider-apache-custom-proxy-configuration.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
// Module included in the following assemblies: | ||
// | ||
// * authentication/identity_providers/configuring-request-header-identity-provider.adoc | ||
|
||
[id="identity-provider-apache-custom-proxy-configuration_{context}"] | ||
= Custom proxy configuration | ||
|
||
Using the `mod_auth_gssapi` module is a popular way to configure the Apache | ||
authentication proxy using the request header identity provider; however, it is | ||
not required. Other proxies can easily be used if the following requirements are | ||
met: | ||
|
||
* Block the `X-Remote-User` header from client requests to prevent spoofing. | ||
* Enforce client certificate authentication in the `RequestHeaderIdentityProvider` | ||
configuration. | ||
* Require the `X-Csrf-Token` header be set for all authentication requests using | ||
the challenge flow. | ||
* Make sure only the `/oauth/authorize` endpoint and its subpaths are proxied; | ||
redirects must be rewritten to allow the backend server to send the client to | ||
the correct location. | ||
* The URL that proxies to `\https://<namespace_route>/oauth/authorize` must end | ||
with `/authorize` with no trailing slash. For example, `\https://proxy.example.com/login-proxy/authorize?...` | ||
must proxy to `\https://<namespace_route>/oauth/authorize?...`. | ||
+ | ||
* Subpaths of the URL that proxies to `\https://<namespace_route>/oauth/authorize` | ||
must proxy to subpaths of `\https://<namespace_route>/oauth/authorize`. For | ||
example, `\https://proxy.example.com/login-proxy/authorize/approve?...` must | ||
proxy to `\https://<namespace_route>/oauth/authorize/approve?...`. | ||
|
||
[NOTE] | ||
==== | ||
The `\https://<namespace_route>` address is the Route to the OAuth server and | ||
can be obtained by running `oc get route -n openshift-authentication`. | ||
==== |
Oops, something went wrong.