-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.12
-
No
-
Proposed
-
False
-
This is a clone of issue OCPBUGS-8381. The following is the description of the original issue:
—
Derscription of problem:
On a hypershift cluster that has public certs for OAuth configured, the console reports a x509 certificate error when attempting to display a token
Version-Release number of selected component (if applicable):
4.12.z
How reproducible:
always
Steps to Reproduce:
1. Create a hosted cluster configured with a letsencrypt certificate for the oauth endpoint. 2. Go to the console of the hosted cluster. Click on the user icon and get token.
Actual results:
The console displays an oauth cert error
Expected results:
The token displays
Additional info:
The hcco reconciles the oauth cert into the console namespace. However, it is only reconciling the self-signed one and not the one that was configured through .spec.configuration.apiserver of the hostedcluster. It needs to detect the actual cert used for oauth and send that one.
- clones
-
OCPBUGS-8381 Console shows x509 error when requesting token from oauth endpoint
- Closed
- is blocked by
-
OCPBUGS-8381 Console shows x509 error when requesting token from oauth endpoint
- Closed
- links to