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

Omit loading X509 key pair in EOS HTTP Client if the scheme is not https #4870

Merged
merged 1 commit into from
Sep 30, 2024

Conversation

jessegeens
Copy link
Contributor

Currently, the EOS HTTP Client always tries to read an X509 key pair from the file system (by default, from /etc/grid-security/host{key,cert}.pem). This makes it harder to write unit tests, as these fail when this key pair is not on the file system (which is the case for the test pipeline as well).

This PR introduces a fix for this problem, by only loading the X509 key pair if the scheme of the EOS endpoint is https. Unit tests can then create a mock HTTP endpoint, which will not trigger the loading of the key pair.

Copy link

update-docs bot commented Sep 30, 2024

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

@jessegeens jessegeens force-pushed the fix/eoshttpclient-tls branch from 39d993e to 772cbac Compare September 30, 2024 09:59
@jessegeens jessegeens force-pushed the fix/eoshttpclient-tls branch from 772cbac to 6c73add Compare September 30, 2024 10:02
@jessegeens jessegeens merged commit a41ea23 into master Sep 30, 2024
16 checks 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