Getting the sameInteresting, seems like for some reason the taglib isn't loading either that specific implementation. IF you look at my code, I have used slign:definobjects     Error during include of component '/apps/imftgsik/components/directorybrowser'Error Message:org.apache.sling.api.scripting....

hey per ~~Feike Visser  if I'm using adaptTo I don't need to close it

No I meant either ways, not that we are opening sessions using both methods. If I just use session using AdaptTo, does that also need to be closed using session.close()

Or it makes sense to use every component like this@Activate  protected void activate() {    session = null;    try {      session = repo.loginAdministrative();      …    } catch (RepositoryException e) {      // log the exception    }  }  @Deactivate  protected void deactivate() {    if (session != ...

Does this apply only while getting an admin session using resolverfactory or even a regular session using resourceResolver.adaptTo(Session.class) using the request object of the servlet?

Got this working. Following was the querypath=/home/users nodename=profiledaterange.property=cq:lastModified    daterange.upperBound=2015-06-06 group.2_group.p.not= true group.2_group.1_property=email group.2_group.1_property.1_value = %domain.org group.2_group.1_property.operation = likep.limit=-1o...

AmitThe query doesn't include the first clause at all. For whatever reason, the first group is being ignoredsee generated xpath/jcr:root/home/users//*[not(((jcr:like(@email, '%mydomain.org'))))and fn:name() = 'profile']order by @email

Kunal,Is that the standard way for AJAX call with parameters?what's btoa in the headers? is that a standard jquery function? Are there other examples of similar ajax calls?

Custom authentication was implemented for us by Adobe Professional Services. We do a bunch of cleanup after logging in including completely destroying old memberships and creating new ones etc. Lars (below in the thread) recommended using com.adobe.granite.auth.saml.util to achieve the same results....

I used this and it's working as expected now                          /* Retrieving User authorizable instance */            Authorizable auth = userManager.getAuthorizable(userInfo.getUserId());            final ResourceResolver resolver = resolverFactory.getAdministrativeResourceResolver(null);   ...