-
Feature
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
-
False
-
Not Selected
-
0% To Do, 0% In Progress, 100% Done
-
0
Feature Overview (aka. Goal Summary)
Currently today we rely on customer fetching the OIDC thumbprint locally when using ROSA clients. This results in users behind proxies, providing OCM with an incorrect thumbprint.
This has resulted in multiple support cases, and engineering toil in fixing. To ensure we mitigate future issues like this we should fetch the thumbprint on OCM server side, to ensure the correct thumbprint is supplied to OIDC configs.
Goals (aka. expected user outcomes)
- As a ROSA User behind a proxy I should be able to create OIDC config, and OIDC providers with the correct thumbprint
Requirements (aka. Acceptance Criteria):
- The OIDC thumbprint should be correct regardless of users local networking
Background
As mentioned above, this has resulted in many support cases and issues, causing toil for all parties, as well as a poor customer experience as they suffer from usability issues with their ROSA clusters