This Request for Enhancement (RFE) proposes enabling the Red Hat Console to be accessed using multiple distinct URLs across different domains. The goal is to improve flexibility for organizations managing various environments, brands, or regions, allowing users to securely reach the same console instance through domain-specific entry points without configuration conflicts.

OpenShift currently lacks support for multiple console URLs that could provide independent access to the OpenShift Container Platform (OCP) console via distinct domain names. This limitation also applies to OAuth. However, it remains feasible to establish custom routes with a different Fully Qualified Domain Name (FQDN) that will redirect traffic to the original console URL/domain after successful OAuth authentication through the default OpenShift Oauth mechanism.

The fundamental challenge stems from OpenShift's authentication system, which is architected with a single, canonical OAuth server URL defined within the cluster's configuration. When a user accesses the console from either the original or a new URL, the application consistently retrieves its authentication metadata from the cluster's API, which exclusively contains the primary OAuth URL. Consequently, regardless of the console URL employed, all authentication requests will be redirected to the singular, default OAuth server. Therefore, the desired outcome of having a new console URL redirect to a new OAuth URL, while the original URLs retain independence, is not achievable.

It is still possible to overwrite the original console URL/domain by following the instructions provided in this article. By implementing this, console requests originating from the original console domain will be redirected to the new domain, though authentication will continue to utilize the default OAuth.