Custom branding fails with proxy access in OIDC mode

[GoebelL]

Version Info 19.1 RC1

Describe the bug Configured OSCM reverse proxy in OIDC mode brings timeout with custom brandings.
proxy.conf

 ... 
 location /custom-branding {
        proxy_pass https://oscm-branding:443/custom-branding/;
        proxy_set_header Host            $host;
        proxy_set_header X-Forwarded-For $remote_addr;
        client_max_body_size 50m;
  }

How to Reproduce Steps to reproduce the behavior:

1. Setup OSCM with OIDC and proxy
2. Deploy custom branding at /docker/config/brandings/custom-branding
3. Add another rule in proxy.conf for proxying custom branding URLs
4. Connect your marketplace with custom branding
5. Access the marketplace via the FQDN URL

Expected behavior My nicely customized marketplace landing page

Observed behavior Gateway Timeout

Screenshots Not needed

Additional context Ask me

[GoebelL]

Related issue https://github.com/servicecatalog/oscm/issues/1188

[GoebelL]

Status

1. The proxy is working well as before
2. The gateway timeout with custom branding is fixed with OIDC filter exclusion in https://github.com/servicecatalog/oscm/pull/1195.
3. The provisioning is fixed with servicecatalog/oscm#1188