git.iko.soy/typeable/oauth2-proxy
on master help sign in
Update release notes for v3.1.0
commit5b95ed35522caf9eda8bcf72be824a0c4ed49ac4 authorJoel Speed <Joel.speed@hotmail.co.uk> dateFri 8 Feb 2019, 11:57 (8 years ago) parent402ce6f
2 files changed+27−8
compare with master
unifiedsplit
CHANGELOG.md+19 README.md+8−8
CHANGELOG.md+19
@@ -1,5 +1,24 @@
11# Vx.x.x (Pre-release)
22
3+## Changes since v3.1.0
4+
5+# v3.1.0
6+
7+## Release highlights
8+
9+- Introduction of ARM releases and and general improvements to Docker builds
10+- Improvements to OIDC provider allowing pass-through of ID Tokens
11+- Multiple redirect domains can now be whitelisted
12+- Streamed responses are now flushed periodically
13+
14+## Important notes
15+
16+If you have been using [#bitly/621](https://github.com/bitly/oauth2_proxy/pull/621)
17+and have cookies larger than the 4kb limit,
18+the cookie splitting pattern has changed and now uses `_` in place of `-` when
19+indexing cookies.
20+This will force users to reauthenticate the first time they use `v3.1.0`.
21+
322## Changes since v3.0.0
423
524- [#14](https://github.com/pusher/oauth2_proxy/pull/14) OIDC ID Token, Authorization Headers, Refreshing and Verification (@joelspeed)
README.md+8−8
@@ -19,17 +19,17 @@ A list of changes can be seen in the [CHANGELOG](CHANGELOG.md).
1919
20201. Choose how to deploy:
2121
22− a. Download [Prebuilt Binary](https://github.com/pusher/oauth2_proxy/releases) (current release is `v3.0.0`)
22+ a. Download [Prebuilt Binary](https://github.com/pusher/oauth2_proxy/releases) (current release is `v3.1.0`)
2323
2424 b. Build with `$ go get github.com/pusher/oauth2_proxy` which will put the binary in `$GOROOT/bin`
2525
26− c. Using the prebuilt docker image [quay.io/pusher/oauth2_proxy](https://quay.io/pusher/oauth2_proxy)
26+ c. Using the prebuilt docker image [quay.io/pusher/oauth2_proxy](https://quay.io/pusher/oauth2_proxy) (AMD64, ARMv6 and ARM64 tags available)
2727
2828Prebuilt binaries can be validated by extracting the file and verifying it against the `sha256sum.txt` checksum file provided for each release starting with version `v3.0.0`.
2929
3030```
3131sha256sum -c sha256sum.txt 2>&1 | grep OK
32−oauth2_proxy-3.0.0.linux-amd64: OK
32+oauth2_proxy-3.1.0.linux-amd64: OK
3333```
3434
35352. Select a Provider and Register an OAuth Application with a Provider
@@ -427,19 +427,19 @@ server {
427427 auth_request_set $auth_cookie $upstream_http_set_cookie;
428428 add_header Set-Cookie $auth_cookie;
429429
430− # When using the --set-authorization flag, some provider's cookies can exceed the 4kb
431− # limit and so the OAuth2 Proxy splits these into multiple parts.
430+ # When using the --set-authorization flag, some provider's cookies can exceed the 4kb
431+ # limit and so the OAuth2 Proxy splits these into multiple parts.
432432 # Nginx normally only copies the first `Set-Cookie` header from the auth_request to the response,
433433 # so if your cookies are larger than 4kb, you will need to extract additional cookies manually.
434434 auth_request_set $auth_cookie_name_upstream_1 $upstream_cookie_auth_cookie_name_1;
435−
435+
436436 # Extract the Cookie attributes from the first Set-Cookie header and append them
437437 # to the second part ($upstream_cookie_* variables only contain the raw cookie content)
438438 if ($auth_cookie ~* "(; .*)") {
439− set $auth_cookie_name_0 $auth_cookie;
439+ set $auth_cookie_name_0 $auth_cookie;
440440 set $auth_cookie_name_1 "auth_cookie_name_1=$auth_cookie_name_upstream_1$1";
441441 }
442−
442+
443443 # Send both Set-Cookie headers now if there was a second part
444444 if ($auth_cookie_name_upstream_1) {
445445 add_header Set-Cookie $auth_cookie_name_0;