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

Pass client certificate and SNI to auth service #5823

Merged
merged 3 commits into from
Feb 14, 2025
Merged

Pass client certificate and SNI to auth service #5823

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9b68942
Pass client certificate and SNI to auth service
isker Feb 11, 2025
6c161bd
Move CHANGELOG tweak into docs/releaseNotes.yml
kflynn Feb 13, 2025
2ae7171
Automatic formatter stuff
kflynn Feb 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,12 @@ it will be removed; but as it won't be user-visible this isn't considered a brea
- Feature: Emissary-ingress now supports resolving Endpoints from EndpointSlices in addition to the
existing support for Endpoints, supporting Services with more than 1000 endpoints.

- Feature: Emissary-ingress now passes the client TLS certificate and SNI, if any, to the external
auth service. These are available in the `source.certificate` and `tls_session.sni` fields, as
described in the <a
href="https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/auth/v3/attribute_context.proto">
Envoy extauth documentation</a>.

[Incorrect Cache Key for Mapping]: https://github.com/emissary-ingress/emissary/issues/5714

## [3.9.0] November 13, 2023
Expand Down
Loading
Loading