Repository navigation
Require TLS for the production scheduler API - #22
Merged
Merged
Conversation
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
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.
Apollo previously sent service credentials over plaintext gRPC. Require a mounted server certificate and key, serve TLS 1.2 or newer, and reject production plaintext fallback. Nonproduction fixtures can explicitly opt out; migrations remain independent of listener configuration.
Validation: Azure race tests passed for server and command packages. A real gRPC/TLS test delivered credentials over a trusted connection and rejected the wrong hostname and CA before the request reached the service. Production missing/invalid configuration and conflicting plaintext settings fail closed. App-client TLS and deployment certificate wiring are being qualified separately.