For this specific BZ, the change is we moved the OAuth workflow from being pure client side on browser to now occurring mostly on the backend nodejs app serving the UI. QE: Please focus on verifying UI works as you expect, i.e. no regressions as you run through regular UI workflows in non-IBM ROKS environments. This change is not sufficient to resolve MTC UI operating on IBM ROKS, there is a larger concern of not being able to configure the k8s API Server headers to specify crossOriginAllowed headers for our UI. We have a RFE requesting ability to configure CORS in IBM ROKS, tracked via: ‘HOSTEDCP-66'. It is unlikely to be resolved soon, we may want to consider implementing a proxy of all UI interaction to k8s api server to workaround the CORS issues. We will use BZ 1878824 to track the larger issue of MTC UI not working in IBM ROKS environment.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Migration Toolkit for Containers (MTC) tool image release advisory 1.3.2), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:5133