The authentication operator is not respecting the default branding config that https://github.com/openshift/origin-branding/blob/master/manifests/0000_10_origin-branding_configmap.yaml lays down. This supersedes the previous branding configuration users did with a payload innate mechanism, and the login page needs to respect the default here (this is a default, does not override user input). This is a release blocker.
Specifically, the login page should default to OCP display, and the presence of this config location on the cluster should inform the operator to use Origin if it exists and the user has not provided a config.
https://jira.coreos.com/browse/AUTH-265
First PR of a series: Fix the embedded object within the configmap: https://github.com/openshift/origin-branding/pull/5
2nd pr to fix the auth-operator: https://github.com/openshift/cluster-authentication-operator/pull/121
Login page template updated with new logo in https://github.com/openshift/ose/pull/1521
https://github.com/openshift/cluster-authentication-operator/pull/124 PR is in the merge queue.
PR merged.
Verified on 4.1.0-0.nightly-2019-05-06-011159
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, 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-2019:0758