Assuming admin_gui_session_conf is set appropriately and we are confident in the OIDC configuration (worked elsewhere):
The issue stems from making use of HTTP/2 with passthrough OpenShift Routes and having the same SSL certificate bound to those routes.
In OpenShift, if you are doing the above, it will attempt to coalesce the connections and you will effectively see it criss-crossing (sending requests meant for the Admin API to the Manager, and vice versa).
This leads to the issues stated above and logging in will not function.
Details of this can be found here:
“To enable the use of HTTP/2 for the connection from the client to HAProxy, a route must specify a custom certificate. A route that uses the default certificate cannot use HTTP/2. This restriction is necessary to avoid problems from connection coalescing, where the client re-uses a connection for different routes that use the same certificate.”
To remedy the situation, you can take one of two actions:
1) Ensure that your OpenShift Routes all make use of different SSL certificates
2) Turn off HTTP/2 when using passthrough OpenShift Routes with the same SSL certificate