1. Proposed title of this feature request

Support to expose api/console/oauth behind a reverse proxy

2. What is the nature and description of the request?

It is needed a consolidated and supported way to expose the OpenShift api/console/oauth placed behind a reverse proxy.

The well-known/authorization_endpoints of the API must be based on Customer reverse proxy and not based on the default basedomain of the OCP

On the console homepage, there is some login, logout etc... url provided in javascript that redirect to the basedomain of OCP and not the customer's revers proxy

There is also some limitation due to the different Origin/Location headers used

Helpful links:

Found a discussion regarding this issue with some nginx configuration suggestions.

https://access.redhat.com/discussions/6211811

3. Why does the customer need this? (List the business requirements here)

Customer wants to place a reverse proxy before ocp api/console/oauth.

This RFE is coming from a new ESS Shift Customer