New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[management-api] Performance issue when searching for users in LDAP #654

Closed
brasseld opened this Issue Jun 22, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@brasseld
Member

brasseld commented Jun 22, 2017

In some case, when searching for a user to manage API / application members, it can take a very long time before getting a response from the server which results on messages at the portal level saying that the server is unreachable.

Also, searching for users from a big LDAP may return a very long list of results when you're searching using a single letter or a few letter.

Finally, when I'm searching for 'bra', three searches are done: 'b', 'br', 'bra'. This results on many useless requests with large results...

@brasseld brasseld added this to the 1.8.0 milestone Jun 22, 2017

@brasseld brasseld self-assigned this Jun 22, 2017

brasseld added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Jun 22, 2017

fix(ldap): Set the maximum number of results and the time use to quer…
…y LDAP

Also, we ask the LDAP to get back only required attributes and not all attributes linked to the user

Closes gravitee-io/issues#654

brasseld added a commit to gravitee-io/gravitee-management-webui that referenced this issue Jun 22, 2017

tcompiegne added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Jul 6, 2017

fix(ldap): Set the maximum number of results and the time use to quer…
…y LDAP

Also, we ask the LDAP to get back only required attributes and not all attributes linked to the user

Closes gravitee-io/issues#654

tcompiegne added a commit to gravitee-io/gravitee-management-webui that referenced this issue Jul 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment