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.

Sign up for GitHub

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

Jump to bottom

Verify PSC DNS name is present as a SAN in the server certificate #499

Open
ttosta-google opened this issue Apr 8, 2024 · 0 comments
Open

Verify PSC DNS name is present as a SAN in the server certificate #499

ttosta-google opened this issue Apr 8, 2024 · 0 comments
Assignees
@nancynh
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern.

Comments

@ttosta-google
Copy link
Contributor

ttosta-google commented Apr 8, 2024 •
edited
Loading

Verify PSC DNS name is present as a SAN in the server certificate. It means removing the existing workaround to check the private IP address instead of the DNS name (#448).
@ttosta-google ttosta-google added priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern. labels Apr 8, 2024
@ttosta-google ttosta-google assigned enocom and unassigned ttosta-google Apr 9, 2024
@nancynh nancynh assigned nancynh and unassigned enocom May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nancynh nancynh

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@enocom @nancynh @ttosta-google