After adding LDAP configuration to the Quay config editor, the editor fails to validate, only returning a client side error that resembles a timeout. Bypassing the config editor and adding the configuration details directly to the config.yaml results in validation successfully passing in the container and the Quay cluster successfully starting up. I believe the issue may be related to an Nginx timeout, as the validation in the container does take a good few moments to trigger. Authentications are quick and responsive, so I do not believe it is the customer's LDAP environment that is resulting in the issue. I've now seen this with two different customers and I believe the issue is with the config editor. 

For reference, previous chat logs: https://coreos.slack.com/archives/C7WH69HCY/p1615903876008400