Skip to content
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.

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

Improve usage of OIDC_TLS_VERIFY #78

Merged
merged 2 commits into from
Nov 13, 2023
Merged

Conversation

ServiusHack
Copy link
Contributor

When trying to use the oidc-test-client with an OIDC provider running locally behind a self-signed certificate I ran into two minor issues. Created two small commits to fix those.

  • OIDC_TLS_VERIFY had inverted logic
  • The configuration didn't apply for the initial requests

When OIDC_TLS_VERIFY was set to the string "true" this was converted
to the boolean `true` by `strToBool`. This resulted in `skipTLSVerify`
also returning `true`. Thus verification was actually skipped.

Fixed this inverted logic bug.
The configuration OIDC_TLS_VERIFY was only applied to for the refresh-
token related checks. It was still not possible to use the test client
with an OIDC provider that was using a self-signed certificate.

This commit changes the context used for communicating with the OIDC
provider. That way TLS certificate validation can be skipped and thus
an OIDC provider using a self-signed certificate can also be used.
@BeryJu BeryJu merged commit a64dd56 into BeryJu:main Nov 13, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants