From the RFE Template: > 1. Proposed title of this feature request Add to the status how the router should be reached > 3. What is the nature and description of the request? The customer wanted to deploy multiple routers in the same node using different ports but when deploying applications like Jenkins or RH-SSO the authentication redirect was taking the user to the wrong port. > 4. Why does the customer need this? (List the business requirements here) The only known way to overcome this is by changing the serviceaccount either manually or at the template level. serviceaccounts.openshift.io/oauth-redirectreference.second: {"kind":"OAuthRedirectReference","apiVersion":"v1","reference":{"kind":"Route","name":"jenkins"}}' serviceaccounts.openshift.io/oauth-redirecturi.second: //:11443 > 5. How would the customer like to achieve this? (List the functional requirements here) As a user I want to be able to configure a firewall/proxy externally and my routers to be deployed on different ports (e.g. 11443). Then, when I deploy an application which takes the redirect url from the router status, the application would know where to redirect, including the port. - Currently the oauth URL would be: https://openshift.example.com:8443/oauth/authorize?client_id=system:serviceaccount:test:jenkins&redirect_uri=https://jenkins-test.apps.example.com:11443/securityRealm/finishLogin&response_type=code&scope=user:info%20user:check-access&state=NWFlOWI0ODgtOGM3Ny00 - The expected redirect_uri should use port 443 instead > 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Jenkins or any other application using OAuth should be capable of getting the right redirect url from the additional information added to the either the route or the router status. > 10. List any affected packages or components. Router
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers. Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant. This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.