Authorization header conflict with rabbitmq admin ui when using OIDC filter

[scottillogical]

Hey folks I am trying to allow http access to a rabbitmq admin UI.
When using port forwarding, everything works fine, but when using edge stack to route requests to the rabbitmq admin, the login form is displayed but the authentication request returns a 401 when an oidc filter is enabled regardless of whether remove_request_headers is set or not

Typically we have this set in this scenario

remove_request_headers
- authorization

However the 401 is still present

My question is is there a way to workaround the request header conflict on a particular mapping? I still want OIDC to work, I just don't want to pass the request headers on to the application.