-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.15.z
This is a clone of issue OCPBUGS-38065. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-38062. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-37052. The following is the description of the original issue:
—
Description of problem:
This is a followup of https://issues.redhat.com/browse/OCPBUGS-34996, in which comments led us to better understand the issue customers are facing. LDAP IDP traffic from the oauth pod seems to be going through the configured HTTP(S) proxy, while it should not due to it being a different protocol. This results in customers adding the ldap endpoint to their no-proxy config to circumvent the issue.
Version-Release number of selected component (if applicable):
4.15.11
How reproducible:
Steps to Reproduce:
(From the customer) 1. Configure LDAP IDP 2. Configure Proxy 3. LDAP IDP communication from the control plane oauth pod goes through proxy instead of going to the ldap endpoint directly
Actual results:
LDAP IDP communication from the control plane oauth pod goes through proxy
Expected results:
LDAP IDP communication from the control plane oauth pod should go to the ldap endpoint directly using the ldap protocol, it should not go through the proxy settings
Additional info:
For more information, see linked tickets.
- clones
-
OCPBUGS-38065 [release-4.15] LDAP communication going through HTTP(S) proxy
- Closed
- is blocked by
-
OCPBUGS-38065 [release-4.15] LDAP communication going through HTTP(S) proxy
- Closed
- links to
-
RHBA-2024:7184 OpenShift Container Platform 4.14.z bug fix update