-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add mTLS and AuthorizedGroups
support
#3
Merged
Merged
Conversation
This file contains 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
…and a least-connection load balancer. Yet to be implemented: mTLS authn/z and RateLimiting
- Comments and consolidation of Config - Simplify connection handling in proxy with less channels + goroutines
…ancer implementation.
…setting a sleep in the echo server, and confirmed the tests failed, logging the i/o timeout. It is possible this doesn't work exactly how I think, in that long-lived connections that don't send some type of heartbeat might expire. Will test that once I have the server component. ``` ❯ make test go test ./... 2024/02/28 21:27:59 INFO proxy ready listening=127.0.0.1:61459 targets=127.0.0.1:61458 2024/02/28 21:28:01 ERROR idle timeout exceeded error="readfrom tcp 127.0.0.1:61459->127.0.0.1:61460: read tcp 127.0.0.1:61461->127.0.0.1:61458: i/o timeout" 2024/02/28 21:28:01 ERROR copying data error="readfrom tcp 127.0.0.1:61459->127.0.0.1:61460: read tcp 127.0.0.1:61461->127.0.0.1:61458: i/o timeout" 2024/02/28 21:28:01 ERROR idle timeout exceeded error="readfrom tcp 127.0.0.1:61461->127.0.0.1:61458: read tcp 127.0.0.1:61459->127.0.0.1:61460: i/o timeout" 2024/02/28 21:28:01 ERROR copying data error="readfrom tcp 127.0.0.1:61461->127.0.0.1:61458: read tcp 127.0.0.1:61459->127.0.0.1:61460: i/o timeout" ```
… on connection closing to prevent a goroutine from getting stuck. Simplify the public API.
This configures the proxy to listen with TLS, with mutual TLS between it and the client, and vice versa. * Provided certificates with the repo to make it easy to run and connect to the proxy. * Two user certificates provided, with two different groups, with tests confirming unauthorized clients have their connection closed. * Certificates are generated with SAN that supports `localhost` and `127.0.0.1` for the server name.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This configures the proxy to listen with TLS, with mutual TLS between it and the client, and vice versa.
localhost
and127.0.0.1
for the server name.