Comment 3 for bug 1830307

From discussion on the proposed fix, this seems to actually be an issue of an incorrectly configured keystone deployment and not an issue with the sqlalchemy version. Using the user_enabled_mask ldap config option is the correct fix for converting an integer returned from the ldap schema to a boolean that sqlalchemy can use.

Marking this bug as incomplete to leave it open for other operators to signal that this affects them too and deserves an upstream fix, otherwise this bug will expire.