Bug 1677587
| Summary: | Could not handle invalid LDAP IDP configuration | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Chuan Yu <chuyu> |
| Component: | apiserver-auth | Assignee: | Sally <somalley> |
| Status: | CLOSED DUPLICATE | QA Contact: | scheng |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | aos-bugs, chuyu, evb, mkhan, slaznick |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-04-05 13:43:14 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I agree that the missing validation is a problem that we know of and is currently tracked in https://jira.coreos.com/browse/AUTH-201. However, please do specify why the config is invalid so that anyone looking at the BZ knows what's happening. *** This bug has been marked as a duplicate of bug 1696115 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: When configure invalid LDAP IDP, the authentication pods still could start successfully Version-Release number of selected component (if applicable): RHCOS build: Build 47.315 OCP: release:4.0.0-0.nightly-2019-02-13-204401 How reproducible: always Steps to Reproduce: 1.configure LDAP IDP with invalid configuration, such as identityProviders: - challenge: true ldap: attributes: id: - dn name: - cn preferredUsername: - uid ca: {} insecure: true url: ldaps://ldap.forumsys.com/dc=example,dc=com?uid login: true mappingMethod: claim name: testldap type: LDAP 2. 3. Actual results: The authentication pods start successfully Expected results: Error report and the authentication pods could not start successfully. Additional info: