Skip to content
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

Auth: add explicit SNI name support for ExtensionService #2893

Closed
jpeach opened this issue Sep 9, 2020 · 2 comments
Closed

Auth: add explicit SNI name support for ExtensionService #2893

jpeach opened this issue Sep 9, 2020 · 2 comments
Labels
area/tls Issues or PRs related to TLS support. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@jpeach
Copy link
Contributor

jpeach commented Sep 9, 2020

Please describe the problem you have

The ExtensionService processing configures Envoy to send a SNI server name when upstream TLS validation is enabled. However, there may be cases where you need to send a different name than you validate or you want to send the name but not validate.

Two options seem appropriate:

  1. Allow upstream validation with just a server name (CA secret omitted). This is the same API as now, but easier to use.
  2. Add a new field to set the SNI name. This adds API complexity and flexibility.
Copy link

github-actions bot commented Jan 9, 2024

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 9, 2024
Copy link

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tls Issues or PRs related to TLS support. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant