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

Ability to pass client certificate to backend #3402

Open
Exobitt opened this issue Oct 22, 2024 · 3 comments
Open

Ability to pass client certificate to backend #3402

Exobitt opened this issue Oct 22, 2024 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Exobitt
Copy link

Exobitt commented Oct 22, 2024

What would you like to be added:
The ability to pass client certificates to the backend when using frontendValidation within the Gateway resource.
The path is: spec.listeners.tls.frontendValidation.
When this is enabled, the frontend prompts the client to provide their certificate, which should then be passed to the backend services in a header.

Why this is needed:
In a lot of scenarios, some applications needs a client certificate. This is a standard procedure, a lot of other ingress controllers has.

@Exobitt Exobitt added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 22, 2024
@howardjohn
Copy link
Contributor

Are you talking about XFCC or something else?

@Exobitt
Copy link
Author

Exobitt commented Oct 23, 2024

Are you talking about XFCC or something else?

Exactly that, yes.
In Traefik its X-Forwarded-Tls-Client-Cert.
Apparently, Envoy is X-Forwarded-Client-Cert

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. 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

4 participants