Skip to content

Add doc for OPENSHIFT_OAUTH_REQUEST_HEADER_CA_FILE #211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adellape merged 1 commit into from
Mar 9, 2015
Merged

Add doc for OPENSHIFT_OAUTH_REQUEST_HEADER_CA_FILE #211

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion architecture/authentication.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -190,7 +190,7 @@ Multiple headers can be specified using a comma-separated list. Each header is c

`OPENSHIFT_OAUTH_REQUEST_HEADERS` defaults to `X-Remote-User`

TODO: Add options to verify the request (e.g. client certificate checking, IP range restriction, etc) to ensure it is coming from a trusted source before using the username in the request header.
To require requests to present a valid client certificate, set the `OPENSHIFT_OAUTH_REQUEST_HEADER_CA_FILE` environment variable to the path to a PEM-encoded certificate bundle. If set, a valid client certificate must be presented and validated against the certificate authorities in the specified file before the request headers are checked for usernames.

==== Session configuration [[config-session]]

Expand Down Expand Up @@ -308,6 +308,11 @@ OPENSHIFT_OAUTH_HANDLER=deny
```
The authenticating proxy can use whatever authentication method it likes, but keep in mind that both browser and non-browser clients will need to authenticate against it.

To require the proxy to present a client certificate (and ignore `Remote-User` headers unless a valid client certificate is presented):
```
OPENSHIFT_OAUTH_REQUEST_HEADER_CA_FILE=/path/to/certificate_authority_bundle.crt
```

==== Google OAuth provider

To use Google as an identity provider:
Expand Down