"failed to find PEM block" after successfully configuring ingress controller with custom certs on OCP 4.6.4

I have a custom wildcard cert, which I managed to configure IngressController with, after much struggle. I chained the cert, intermediate cert, root cert and the key into the pem, and only then ingress controller was up and I finally saw that indeed my custom cert is served (for example upon accessing the console route). However, now the oauth-openshift complains that: Copying system trust bundle I0203 14:17:38.623709 1 dynamic_serving_content.go:111] Loaded a new cert/key pair for "serving-cert::/var/config/system/secrets/v4-0-config-system-serving-cert/tls.crt::/var/config/system/secrets/v4-0-config-system-serving-cert/tls.key" F0203 14:17:38.624117 1 cmd.go:49] failed to load SNI cert and key: tls: failed to find PEM block with type ending in "PRIVATE KEY" in key input after skipping PEM blocks of the following types: [CERTIFICATE CERTIFICATE CERTIFICATE] g I take it that the ingress controller operator, upon creation of my custom cert secret, also updates the v4-0-config-system-serving-cert secret that the openshift-oauth uses..? How should the pem be constructed so that both the ingress controller and the oauth pod are at peace?