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

Provider is nil if oidc unresolvable #631

Closed
Cyb3rDudu opened this issue Sep 30, 2020 · 1 comment
Closed

Provider is nil if oidc unresolvable #631

Cyb3rDudu opened this issue Sep 30, 2020 · 1 comment
Labels
Category:Defect Existing functionality is not working as expected Type:Bug

Comments

@Cyb3rDudu
Copy link
Contributor

oidcProvider = provider

needs graceful exit if provider still nil.

Reproducible by using docker and ufw firewall. Reasons not exactly clear.
Docker container is not able to resolve own domain due to firewall mess-up.

@Cyb3rDudu Cyb3rDudu added the bug label Sep 30, 2020
@settings settings bot removed the bug label Jan 12, 2021
@refs refs added the Category:Defect Existing functionality is not working as expected label Jan 13, 2021
@settings settings bot removed the p3-medium label Apr 7, 2021
@rhafer
Copy link
Contributor

rhafer commented Aug 4, 2022

This has been fixed a while ago (part of #877) in the proxy middleware. The oidc middleware in ocis-pkg does not exist anymore.

@rhafer rhafer closed this as completed Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category:Defect Existing functionality is not working as expected Type:Bug
Projects
None yet
Development

No branches or pull requests

3 participants