Description of problem:

Using version 1.0.2-1.el7 of ovirt-engine-extension-aaa-ldap, along with ovirt-engine 3.5.3.1. LDAP authentication is configured in the following way:

aaa/mydomain.properties
=======================
include = <rfc2307-openldap.properties>
vars.server = openldap.domain.com
vars.user =
vars.password =
pool.default.serverset.srvrecord.service = ldaps
pool.default.serverset.srvrecord.protocol = tcp
pool.default.serverset.single.server = ${global:vars.server}
pool.default.auth.simple.bindDN = ${global:vars.user}
pool.default.auth.simple.password = ${global:vars.password}
pool.default.ssl.startTLS = false
sequence-init.init.100-my-basedn-init-vars = my-basedn-init-vars
sequence.my-basedn-init-vars.010.description = set baseDN
sequence.my-basedn-init-vars.010.type = var-set
sequence.my-basedn-init-vars.010.var-set.variable = simple_baseDN
sequence.my-basedn-init-vars.010.var-set.value = cn=Users,dc=mydomain,dc=com
search.default.search-request.derefPolicy = ALWAYS
Version-Release number of selected component (if applicable):

extensions.d/mydomain-authn.properties
======================================
ovirt.engine.extension.name = mydomain-authn
ovirt.engine.extension.bindings.method = jbossmodule
ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine-extensions.aaa.ldap
ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engineextensions.aaa.ldap.AuthnExtension
ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.aaa.Authn
ovirt.engine.aaa.authn.profile.name = mydomain
ovirt.engine.aaa.authn.authz.plugin = mydomain-authz
config.profile.file.1 = ../aaa/mydomain.properties

extensions.d/mydomain-authz.properties
======================================
ovirt.engine.extension.name = mydomain-authz
ovirt.engine.extension.bindings.method = jbossmodule
ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine-extensions.aaa.ldap
ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engineextensions.aaa.ldap.AuthzExtension
ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.aaa.Authz
config.profile.file.1 = ../aaa/mydomain.properties

We have all users under the same cn (cn=Users). Our users were all in the format uid=XXXYYYYYYYYYY, where X are letters and Y are numbers (e.g.: uid=bbb101234567,cn=Users,dc=mydomain,dc=com). In this case it works just fine. 

But recently we had to add some special users whose uid are just numbers (e.g.: uid=101234567,cn=Users,dc=mydomain,dc=com). In that case, the LDAP search in the ovirt manager will try to find the user and return no results, although the user indeed exists.

How reproducible:
Always if the uid is in only-numbers format.

Steps to Reproduce:
1. Go to tab 'Permissions'
2. Click on 'Add'
3. Select the base DN, and enter an uid formed of numbers to be added (for example 101234567) in the search box
4) Click on 'GO'

Actual results:
No result is returned, although the user exists in the LDAP database.

Expected results:
The existing user.