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

Always deny requests of failed auth configurations #819

Merged
merged 1 commit into from
Jul 10, 2021

Conversation

jcmoraisjr
Copy link
Owner

The attempt to configure auth external or oauth means that the backend should be protected. However the current implementation is leaving the backend unprotected if a misconfiguration is found - which can be an external failure like a dns lookup. This update ensures that an attempt to protect a backend will in fact protect it, and misconfigurations or failures during the configuration parsing means an always-deny behavior.

The attempt to configure auth external or oauth means that the backend
should be protected. However the current implementation is leaving the
backend unprotected if a misconfiguration is found - which can be an
external failure like a dns lookup. This update ensures that an attempt
to protect a backend will in fact protect it, and misconfigurations or
failures during the configuration parsing means an always-deny behavior.
@jcmoraisjr
Copy link
Owner Author

#817

@jcmoraisjr jcmoraisjr merged commit ba84b76 into master Jul 10, 2021
@jcmoraisjr jcmoraisjr deleted the jm-auth-deny-on-failure branch July 10, 2021 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant