Skip to content

feat: add SSL target name override for gRPC connections - #448

Open
ksmaze wants to merge 3 commits into
triton-inference-server:mainfrom
ksmaze:main
Open

feat: add SSL target name override for gRPC connections#448
ksmaze wants to merge 3 commits into
triton-inference-server:mainfrom
ksmaze:main

Conversation

@ksmaze

@ksmaze ksmaze commented Oct 29, 2025

Copy link
Copy Markdown

To fix: #447

  • Added ssl_grpc_target_name_override option to override TLS hostname verification in gRPC channels
  • Implemented target name override support in Triton and TensorFlow Serving gRPC clients
  • Added command line flag --ssl-grpc-target-name-override with usage documentation
  • Added unit tests to verify target name override functionality
  • Updated SSL options structs to include the new target_name_override field

verified working following installation guide

- Added ssl_grpc_target_name_override option to override TLS hostname verification in gRPC channels
- Implemented target name override support in Triton and TensorFlow Serving gRPC clients
- Added command line flag --ssl-grpc-target-name-override with usage documentation
- Added unit tests to verify target name override functionality
- Updated SSL options structs to include the new target_name_override field
@the-david-oy

Copy link
Copy Markdown
Contributor

CC: @matthewkotila

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.

gRPC triton/tfserve cannot handle SSL certificate with another CN

2 participants