-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Introduce CheckEndpointConnector, implement for OpenShift connector. #2512
base: master
Are you sure you want to change the base?
Conversation
29b843c
to
d5e9bbd
Compare
This might be interesting to you @nabokihms , as it is somewhat similar to #2430 . |
d5e9bbd
to
3e961e8
Compare
Thank you for the PR. It makes sense to me. Generic OIDC connector also works the same way. I will take a look through the code and give detailed feedback next week. |
I've looked through this PR, and, in my opinion, it is not right to add more public interfaces only to use Dex as a library. The best for me is to add optional endpoints health check to the @sagikazarmark, could you also please have a look at this code? |
913d306
to
3c09a4c
Compare
Signed-off-by: Daniel Haus <[email protected]>
…HTTP client injection to use options as well. Signed-off-by: Daniel Haus <[email protected]>
3c09a4c
to
eea20e1
Compare
@nabokihms thanks for the feedback. Let me know what you think about it. |
Thank you for the quick fix, @dhaus67. I'm still waiting for the second opinion here. We need to figure out what to do with this (and probably with further) Openshift Connector improvements. |
@nabokihms @sagikazarmark any update on your end regarding this? |
Overview
Add the ability to check the endpoints used by the connectors. The goal is to give clients the possibility to check whether a connector's endpoints are reachable.
What this PR does / why we need it
The ultimate goal behind is to avoid potential misconfiguration when creating a new connector. Right now, it wouldn't be possible to detect this at the configuration point, but rather only when using the connector to login if you i.e. use dex within your application.
Ideally, we'd like to check this during creation.
Since this would be a major, undesirable change to introduce this during the
Open
method, I've opted to add a new interface which connectors may implement, if they want to offer the functionality to provide such a method.Alternative to the interface choice, we could also decide to make this method exclusive to the openshift connector, similar to the
OpenWithHTTPClient
, to only expose it for library usage.Special notes for your reviewer
Does this PR introduce a user-facing change?