feat: add TLS support for gRPC connections to Dex #86
+72
−2
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 PR adds support for TLS-secured gRPC connections between the gateway and Dex, enabling secure deployments where Dex and the gateway run on different hosts.
Why this matters
Previously, the gateway could only connect to Dex via insecure gRPC, which limited deployment options. With TLS support, Dex and the gateway can now be deployed separately across different hosts or networks while maintaining secure communication.
What's new
The gateway can now establish secure gRPC connections to Dex using mTLS (mutual TLS). This is configured through the
dexGRPCClientsection in the config file, where you can specify:If TLS configuration isn't provided, the gateway falls back to insecure credentials, maintaining backward compatibility with existing setups.
Testing
Tested with both TLS-enabled and insecure configurations to ensure the feature works correctly and doesn't break existing deployments.