@joshwolf@runyontr Tagging you guys as it seems Authservice can not handle multiple "prefix" headers to match, and multiple URIs in "callback_uri" for a single chain. For this issue do we want to have the ability for people to add multiple kiali/jaeger/prometheus/alertmanager URIs to work with authservice or just a single one? Multiple would match the VirtualService support in most packages (istio.hosts sections) but will complicate the authservice chain creation.
Adding support for multiple is possible but will require quite a few changes to the authservice values that a new chain for each URI will have to be created, each with their own declarations for match, callback_uri, client_id, etc.
HAProxy looks to support multiple URIs per acl line so that config should be simpler to add.
Jason Krausechanged title from Authservice Redirect URLs dont respect virtual service name overrides to Authservice Redirect URLs don't respect virtual service name overrides
changed title from Authservice Redirect URLs dont respect virtual service name overrides to Authservice Redirect URLs don't respect virtual service name overrides
@ryan.j.garcia would this be scoped to only BigBang-generated/managed apps that have a VS backed by authservice? Like you said, the secret template would get pretty hair managing it, but it's not out of the question.
Do you have an example values.yaml of one of those apps using multiple hosts?