Git access over HTTPS is broken with LDAP account on Geo secondary

Summary

When using an LDAP account, a user can not git clone over HTTPS from a secondary Geo node

Steps to reproduce

1. Log into primary Geo node with LDAP account
2. git clone a project from the Geo secondary over HTTPS
3. Fill in the correct password when prompted

What is the current bug behavior?

Access denied as if you typed the wrong password.

What is the expected correct behavior?

Cloning into ...

This has a significant impact

Because it completely blocks usage of Geo for a company that is standardizing on HTTPS Git access.

Customer being blocked by this https://gitlab.zendesk.com/agent/tickets/75619