-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat: Support to ory hydra running in secure mode #62
Conversation
ORY Continuous Integration seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Closing due to inactivity |
@aeneasr for curiosity why is this closed? |
sorry my bad |
No problem ;) |
Co-authored-by: Jakub Błaszczyk <[email protected]>
Co-authored-by: Jakub Błaszczyk <[email protected]>
Fail for tls trust store not presented
@Demonsthere I updated PR based on your comments. |
Hi there @fjvierap thanks for the update! I will check as soon as able :) |
It's looking great 👍 The only improvement I can think of is a small test maybe here to create a client with and without trustStore. |
@Demonsthere should I wait for #62 (comment) ? |
TBH I'm conflicted here. After some evaluation I see that we do not have any test that verifies if the hydraClient is created correctly, which should be addressed. However, fixing that seems outside of the scope of this PR. Maybe we should accept this PR as is, and define a task with adding the missing tests? |
According to our contribution guidelines, if it is required for you to verify that the change is doing what it is supposed to do, then asking for a test as a requirement for merging the PR is in scope :) |
For that we will need to move |
imho, |
Could you please check my last 2 commit and let me know if that is you expect? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's looking great! Just a few little improvements ;)
Hi I added the improvements you suggested ;) |
t.Run("should not create client with and wrong tlsTrustStore", func(t *testing.T) { | ||
client, err := helpers.CreateHttpClient(true, "/somefile") | ||
require.NotNil(t, client) | ||
require.NotNil(t, err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we control what error will be returned here, maybe we could check not only if the err is not nil, but if it the one we expect?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed that the new package is not by default included in the makefile target so the tests for it won't run. Could you please add it there? Then we will see if the test are correct :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :)
Thank you! Could you please rebase/merge with master? Then we can merge it right away! |
Co-authored-by: Jakub Błaszczyk <[email protected]>
Co-authored-by: Jakub Błaszczyk <[email protected]>
We have a hydra instance running in https and we cannot use hydra-maester to communicate with our hydra instance. Hence we created this extension which allows:
insecure-skip-verify
argument.github.com/go-openapi/runtime/client
tls client when a certificate loaded astls-trust-store
argument.