Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,070
Community Members
 
Community Events
184
Community Groups

Using the crowd client api 2.2.2, and trying to query for all inactive users (Boolean) fails

We are trying to query crowd for inactive users:

{code}

Collection<searchrestriction> restrictions = new ArrayList<searchrestriction>();

TermRestriction<boolean> test = new TermRestriction<boolean>(UserTermKeys.ACTIVE, MatchMode.EXACTLY_MATCHES, new Boolean(false));

restrictions.add(test);

List<user> tmp = crowdClient.searchUsers(Combine.allOf(restrictions), 0, 1000);

{code}

This give the following error:

{code}

2011-10-31 11:05:23,804 ERROR CrowdUserAccessorDaoImpl:159 - Operation Failed Exception with message Boolean restrictions for property active are not supported

com.atlassian.crowd.exception.OperationFailedException: Boolean restrictions for property active are not supported

at com.atlassian.crowd.integration.rest.service.RestCrowdClient.handleCommonExceptions(RestCrowdClient.java:1084)

at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchUsers(RestCrowdClient.java:466)

at aero.blue.user.dao.crowd.CrowdUserAccessorDaoImpl.fetchUsers(CrowdUserAccessorDaoImpl.java:147)

{code}

Note that we have the same issue with Date restrictions.

2 answers

The trouble though Jeremy is that active is not an attribute of the user but rather some arbitrary property. I've attempted to do something similar here too, but have had to resort to testing for the presense of the active property once fetching the users.

0 votes
Jeremy Largman
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 19, 2011

Here's the code from com.atlassian.crowd.search.ldap.LDAPQueryTranslaterImpl:

    private Filter booleanTermRestrictionAsFilter(final EntityDescriptor entityDescriptor, final PropertyRestriction<Boolean> termRestriction, LDAPPropertiesMapper ldapPropertiesMapper)
    {
        // if boolean term restrictions are for anything other than the group/user active flag, then throw exception
        if (termRestriction.getProperty() != GroupTermKeys.ACTIVE && termRestriction.getProperty() != UserTermKeys.ACTIVE)
        {
            throw new IllegalArgumentException("Boolean restrictions for property " + termRestriction.getProperty().getPropertyName() + " are not supported");
        }
        else
...
    }  

So, it looks like you can't define your own TermRestriction, as it won't match that comparison.

Instead, why not get all users, then query to see if they're active?

From the REST Resources:

&lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;user name="username" expand="attributes"&gt;
  &lt;first-name&gt;First&lt;/first-name&gt;
  &lt;last-name&gt;Last&lt;/last-name&gt;
  &lt;display-name&gt;First Last&lt;/display-name&gt;
  &lt;email&gt;email@email.com&lt;/email&gt;
  &lt;active&gt;true&lt;/active&gt;
  &lt;attributes&gt;
    &lt;link rel="self" href="link_to_user_attributes"/&gt;
  &lt;/attributes&gt;
  &lt;password&gt;
    &lt;link rel="edit" href="link_to_user_password"/&gt; &lt;!-- /user/password?username=&lt;username&gt; --&gt;
    &lt;value&gt;password&lt;/value&gt; &lt;!-- only used when creating a user, otherwise not filled in --&gt;
  &lt;/password&gt;
&lt;/user&gt;

Looks like there's a 'active' attribute there. Maybe you can use that, and assemble a list by adding it to a data structure after iterating through all the users?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events