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:
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.
https://github.com/openshift/cluster-authentication-operator/pull/80
*** 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