-
Notifications
You must be signed in to change notification settings - Fork 97
fix(conductor): add explicit TLS config #2140
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
Add TLS config for conductor when sequencer_uri is https
- Loading branch information
commit 9223320c0148105ee37c70fcfa7be0bec7385008
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -16,6 +16,7 @@ use astria_eyre::eyre::{ | |
| }; | ||
| use tonic::transport::{ | ||
| Channel, | ||
| ClientTlsConfig, | ||
| Endpoint, | ||
| Uri, | ||
| }; | ||
|
|
@@ -38,7 +39,10 @@ impl SequencerGrpcClient { | |
| let uri: Uri = sequencer_uri | ||
| .parse() | ||
| .wrap_err("failed parsing provided string as Uri")?; | ||
| let endpoint = Endpoint::from(uri.clone()); | ||
| let mut endpoint = Endpoint::from(uri.clone()); | ||
| if uri.scheme() == Some(&http::uri::Scheme::HTTPS) { | ||
| endpoint = endpoint.tls_config(ClientTlsConfig::new().with_enabled_roots())?; | ||
|
||
| } | ||
| let inner = SequencerServiceClient::new(endpoint.connect_lazy()); | ||
| Ok(Self { | ||
| inner, | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Is this necessary? Would setting the tls config preclude us from using http? I think we should be able to still connect (just like before)?
Either way, if this does blockhttp, I think I'd prefer to have ane explicit flag that deactivates tls so that one doesn't accidentally provide http instead of https and risk exposing the service to an unchecked endpoint.
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.
good point, I don't believe the TLS config prevents using http. Should not