http_connection_manager: support multiple SAN URIs for XFCC#20724
http_connection_manager: support multiple SAN URIs for XFCC#20724htuch merged 3 commits intoenvoyproxy:mainfrom jacob-delgado:xfcc-multiple-uri
Conversation
|
The core requirement we are asked is to support is I can put this behind a feature toggle if needed to get this merged. I would also like for this to be as a feature toggle in Envoy 1.19-1.21 as well, if possible. Thoughts? |
...when using APPEND_FORWARD and SANITIZE set. Currently XFCC only keeps the first URI in a certificate or a header presented to it. This works fine for most use cases, however, not everyone uses a single URI (typically spiffe:// only). Add every URI present to the 'By=' portion as well as the 'URI=' portion of an XFCC header. Signed-off-by: Jacob Delgado <jacob.delgado@volunteers.acasi.info>
Signed-off-by: Jacob Delgado <jacob.delgado@volunteers.acasi.info>
|
/retest |
|
Retrying Azure Pipelines: |
lizan
left a comment
There was a problem hiding this comment.
Looks good and I don't feel strongly we need a toggle for main branch.
Though I don't think we should backport either even with a toggle but backports are up to stable maintainer @pradeepcrao
|
/assign-from @envoyproxy/senior-maintainers |
|
@envoyproxy/senior-maintainers assignee is @htuch |
…xy#20724) ...when using APPEND_FORWARD and SANITIZE set. Currently XFCC only keeps the first URI in a certificate or a header presented to it. This works fine for most use cases, however, not everyone uses a single URI (typically spiffe:// only). Add every URI present to the 'By=' portion as well as the 'URI=' portion of an XFCC header. Additional Description: Risk Level: Low Testing: Unit and integration tests Docs Changes: Yes. The appropriate http_connection_managers configuration section. Release Notes: Yes Fixes envoyproxy#20723 Signed-off-by: Jacob Delgado <jacob.delgado@volunteers.acasi.info> Signed-off-by: Andre Vehreschild <vehre@x41-dsec.de>
…xy#20724) ...when using APPEND_FORWARD and SANITIZE set. Currently XFCC only keeps the first URI in a certificate or a header presented to it. This works fine for most use cases, however, not everyone uses a single URI (typically spiffe:// only). Add every URI present to the 'By=' portion as well as the 'URI=' portion of an XFCC header. Additional Description: Risk Level: Low Testing: Unit and integration tests Docs Changes: Yes. The appropriate http_connection_managers configuration section. Release Notes: Yes Fixes envoyproxy#20723 Signed-off-by: Jacob Delgado <jacob.delgado@volunteers.acasi.info>
Commit Message:
...when using APPEND_FORWARD and SANITIZE set.
Currently XFCC only keeps the first URI in a certificate or a header presented
to it.
This works fine for most use cases, however, not everyone uses a single
URI (typically spiffe:// only).
Add every URI present to the 'By=' portion as well as the 'URI=' portion of an
XFCC header.
Additional Description:
Risk Level: Low
Testing: Unit and integration tests
Docs Changes: Yes. The appropriate http_connection_managers configuration section.
Release Notes: Yes
Fixes #20723