This repository has been archived by the owner on Jan 24, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
error redeeming code: illegal base64 data #560
Comments
jehiah
added a commit
that referenced
this issue
Mar 25, 2018
Strip JWT base64 padding before parsing. #560
brockoffdev
pushed a commit
to brockoffdev/oauth2_proxy
that referenced
this issue
Jun 11, 2018
EricEllett
pushed a commit
to segmentio/oauth2_proxy
that referenced
this issue
Jun 18, 2018
* upstream/master: (34 commits) Strip JWT base64 padding before parsing. bitly#560 typo(README): Terminiation » Termination Support bcrypt passwords in htpasswd Fix typo in css for the sign in page template more robust ClearSessionCookie() README: fix nginx auth_request example for requests with body providers: iterate across all pages from /user/orgs github endpoint. Test request logging Document request-logging-format option Make request logging format configurable distribution: remove gpm references and update to use dep distribution: create sha256sum.txt file when creating binaries to allow validation of checksums. * update README.md to include instructions on how to verify prebuilt binaries for new releases. Github provider: use login as user options: update options parsing for better handling of incorrect values * don't add in failed compiled regexes for skip auth regex option * improve test coverage for skip auth regex option to handle partial success case * add tests for incorrect upstream options parsing errors Switch from gpm -> dep for dependency management Switch from 18F/hmacauth to mbland/hmacauth providers: update gitlab api endpoint to use latest version, v4 Swap out bmizerany/assert package that is deprecated in favor of stretchr/testify/assert Drop deprecated MyUSA provider. Add OpenID Connect provider name. ...
JoelSpeed
referenced
this issue
in oauth2-proxy/oauth2-proxy
Jun 20, 2018
Since my patch for this issue was merged back in March, I'm closing my own issue here. The actual discussion (however minimal) happened in #561 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I use oauth2_proxy with a custom provider, using login_url, redeem_url, and profile_url. Recently, new proxies stopped working, and simply 500'd when I tried logging in.
I traced this back to #421. My provider puts padding on the JWTs and padding is no longer allowed. I've rolled back to a working version, but would appreciate guidance on how to fix this for the future.
oauth2_proxy.cfg:
The text was updated successfully, but these errors were encountered: