Skip to content

Allow restricting allowed client certificates for RequestHeaderIdentityProvider #1888

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
merged 1 commit into from
Jun 9, 2016
Merged

Allow restricting allowed client certificates for RequestHeaderIdentityProvider #1888

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
22 changes: 14 additions & 8 deletions install_config/configuring_authentication.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -602,14 +602,16 @@ oauthConfig:
challengeURL: "https://www.example.com/challenging-proxy/oauth/authorize?${query}" <5>
loginURL: "https://www.example.com/login-proxy/oauth/authorize?${query}" <6>
clientCA: /path/to/client-ca.file <7>
headers: <8>
clientCommonNames: <8>
- my-auth-proxy
headers: <9>
- X-Remote-User
- SSO-User
emailHeaders: <9>
emailHeaders: <10>
- X-Remote-User-Email
nameHeaders: <10>
nameHeaders: <11>
- X-Remote-User-Display-Name
preferredUsernameHeaders: <11>
preferredUsernameHeaders: <12>
- X-Remote-User-Login
----
<1> This provider name is prefixed to the user name in the request header to
Expand All @@ -633,13 +635,17 @@ replaced with the current query string.
<7> Optional: 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 user names.
<8> Header names to check, in order, for the user identity. The first header containing
<8> Optional: list of common names (`cn`). If set, a valid client certificate with
a Common Name (`cn`) in the specified list must be presented before the request headers
are checked for user names. If empty, any Common Name is allowed. Can only be used in combination
with `clientCA`.
<9> Header names to check, in order, for the user identity. The first header containing
a value is used as the identity. Required, case-insensitive.
<9> Header names to check, in order, for an email address. The first header containing
<10> Header names to check, in order, for an email address. The first header containing
a value is used as the email address. Optional, case-insensitive.
<10> Header names to check, in order, for a display name. The first header containing
<11> Header names to check, in order, for a display name. The first header containing
a value is used as the display name. Optional, case-insensitive.
<11> Header names to check, in order, for a preferred user name, if different than the immutable
<12> Header names to check, in order, for a preferred user name, if different than the immutable
identity determined from the headers specified in `headers`. The first header containing
a value is used as the preferred user name when provisioning. Optional, case-insensitive.
====
Expand Down