Skip to content

Support BackendTLSPolicy SubjectAltNames #3152

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

Open
sjberman opened this issue Feb 20, 2025 · 1 comment
Open

Support BackendTLSPolicy SubjectAltNames #3152

sjberman opened this issue Feb 20, 2025 · 1 comment
Labels
area/security For security best practices enhancement New feature or request
Milestone

Comments

@sjberman
Copy link
Collaborator

sjberman commented Feb 20, 2025

As an NGF user,
I want to specify Subject Alternative (SAN) names for my backends,
So that I can allow multiple alternative names to be present in the backend certificate.

Note: this may not actually be possible with nginx to support a list of SANs. See kubernetes-sigs/gateway-api#3591 which is changing this field to extended for this reason.

We still may want to investigate.

Acceptance

  • Support the SubjectAltNames field in the BackendTLSPolicy
@sjberman sjberman added area/security For security best practices enhancement New feature or request labels Feb 20, 2025
Copy link
Contributor

github-actions bot commented Mar 7, 2025

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the stale Pull requests/issues with no activity label Mar 7, 2025
@sjberman sjberman removed the stale Pull requests/issues with no activity label Mar 11, 2025
@mpstefan mpstefan added this to the v2.1.0 milestone Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security For security best practices enhancement New feature or request
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants