Skip to content

Update troubleshooting section in README.md #35

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
Sep 23, 2021
Merged

Update troubleshooting section in README.md #35

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

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,6 +199,10 @@ Any errors generated by the OpenID Connect flow are logged to the error log, `/v
* Check for `could not be resolved` and `empty JWK set while sending to client` messages in the error log. This is common when NGINX Plus cannot reach the IdP's `jwks_uri` endpoint.
* Check the `map…$oidc_jwt_keyfile` variable is correct.
* Check the `resolver` directive in **openid_connect.server_conf** is reachable from the NGINX Plus host.
* Check for `OIDC authorization code sent but token response is not JSON.` messages in the error log. This is common when NGINX Plus cannot decompress the IdP's response. Try add the following configuration snippet to the `/_jwks_uri` and `/_token` locations in the openid_connect.server_conf file.
```nginx
proxy_set_header Accept-Encoding "gzip";
```

* **Authentication is successful but browser shows too many redirects**
* This is typically because the JWT sent to the browser cannot be validated, resulting in 'authorization required' `401` response and starting the authentication process again. But the user is already authenticated so is redirected back to NGINX, hence the redirect loop.
Expand Down