meutel/oauth2_proxy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Added more context as suggested by JoelSpeed.

Browse Source 
Co-Authored-By: marratj <marrat@marrat.de>
This commit is contained in:
Joel Speed 2019-02-02 12:47:21 +01:00 committed by GitHub
parent c574346086
commit cd37a14fc0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -424,7 +424,11 @@ server {
auth_request_set $auth_cookie $upstream_http_set_cookie; auth_request_set $auth_cookie $upstream_http_set_cookie;
add_header Set-Cookie $auth_cookie; add_header Set-Cookie $auth_cookie;
# if you enabled --set-authorization and your cookies are split into multiple parts, # When using the --set-authorization flag, some provider's cookies can exceed the 4kb
# limit and so the OAuth2 Proxy splits these into multiple parts.
# Nginx normally only copies the first `Set-Cookie` header from the auth_request to the response,
# so if your cookies are larger than 4kb, you will need to extract additional cookies manually.
auth_request_set $auth_cookie_name_upstream_1 $upstream_cookie_auth_cookie_name_1;
# you also need to extract the additional cookies, because $upstream_http_set_cookie # you also need to extract the additional cookies, because $upstream_http_set_cookie
# only contains the first Set-Cookie header from the auth_request. # only contains the first Set-Cookie header from the auth_request.
auth_request_set $auth_cookie_name_upstream_1 $upstream_cookie_auth_cookie_name_1; auth_request_set $auth_cookie_name_upstream_1 $upstream_cookie_auth_cookie_name_1;