Skip to content
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

Remove minimum character requirement from sector uri client search form #201

Closed
nynymike opened this issue Feb 16, 2016 · 9 comments
Closed
Assignees
Labels
Milestone

Comments

@nynymike
Copy link
Contributor

On the https:///identity/sectoridentifier/manage/add

Hitting search is ok, but should be limited to 20 results.

image

@nynymike nynymike added the bug label Feb 16, 2016
@nynymike nynymike added this to the CE 2.4.2 milestone Feb 16, 2016
@nynymike nynymike assigned qbert2k and shekhar16 and unassigned shekhar16 and qbert2k Feb 16, 2016
@shekhar16
Copy link
Collaborator

Fixed : Removed no of character validations and set limit of display search client result.

@yurem
Copy link
Contributor

yurem commented Feb 21, 2016

I think according to issue description we should keep input validation: 2-30 characters. But limit result set to 20 results.

Hitting search is ok, but should be limited to 20 results.

Also I think you can remove lines 264-266:
6218bc8#diff-63759ce348cbb0a769fa7c3fcc2152abR264

Method uses searchClients(String pattern, int sizeLimit) second param wich tell LDAP to return max number of results.

@shekhar16
Copy link
Collaborator

Yes Yuriy ,I already tried with this approach but the display list is not restricted to expected limit, After that i fixed issue with different approach.(which is currently committed in repo.).
I reviewed that searchclient method and it was returning expected limited result but after that in do-while it will increase the result size and exceed the limit.And finally on display the list exceed the size limit.

@shekhar16
Copy link
Collaborator

As per issue heading "Remove minimum character requirement from sector uri client search form"
I removed the character validation.

@yurem
Copy link
Contributor

yurem commented Feb 22, 2016

If LDAP API not working fine we need to open issue to find out core of the issue.
LdapEntryManager.findEntries(String baseDN, Class entryClass, Filter filter, int sizeLimit)
Should return maximum specified number of entries if sizeLimit > 0

@yurem
Copy link
Contributor

yurem commented Feb 22, 2016

Regarding subject of this issue. I think we need to remove only minimum characters validation. Maxim validation should works as before.

@nynymike Can you clarify requirements

@yurem
Copy link
Contributor

yurem commented Feb 22, 2016

@shekhar16 I understand what you wrote about LdapEntryManager.findEntries with sizeLimit

In oxLdap name of the parameter not conform to actual action..

I updated oxLdap. I renamed:
sizeLimit -> searchLimit

And added:
sizeLimit parameter to allow specify how many entries LDAP should return. Now when we do search we do next:

searchRequest.setSizeLimit(sizeLimit);

These are new changes:
GluuFederation/oxCore@e8ebc63#diff-794d10d8e9dc72141ca737ff12142343R213

@yurem
Copy link
Contributor

yurem commented Feb 22, 2016

@shekhar16 can you try to use new method:
findEntries(String baseDN, Class entryClass, Filter filter, int searchLimit, int sizeLimit)

searchLimit = 0 to not use pagination during search

@yurem
Copy link
Contributor

yurem commented Feb 23, 2016

I offer to close it.

I updated validation: a1ef436

And now we uses LDAP to limit search limit

@yurem yurem closed this as completed Feb 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants