Exception with ODSEE when sorting views from the search results.

book

Article ID: 4512

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

With an OOTB View User task, from the search results screen, a first sort by clicking on one column (e.g.: User Id) properly displays the pages

but a second sort on another column (e.g.: last name) fails with:

java.util.NoSuchElementException at com.netegrity.llsdk6.imsimpl.paging.SearchResults.providerSort.

Cause

ODSEE does not support pagedResultsControl and to work around or to fix this issue, you need to turn off the paging.

To determine whether or not paging is used, IM depends on the maxrows and maxpage settings in directory.xml.

When the Ldap Ops object sets the result controls prior to a search, it checks the JNDIPagingContext which has been constructed earlier.

If either page size is present or maximum rows are present, LdapOps states it is doing a paged search.

Environment

User store is ODSEE (Oracle Directory Server Enterprise Edition)

Resolution

Change your directory.xml to something like the element below:

<DirectorySearch maxpagesize="0"  maxrows="0" minsortrules="1"/>