Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Cannot search Users after upgrade to Crowd 2.12

Hello, we have 2 crowd servers, one prod, one dev

I upgraded our dev instance to latest 2.12, followd the upgrade guide and everything seems to be working except for our User search. 

The group search works correctly, connection to our LDAP server is ok, yet the User search fails, the settings for the search are exactly the same as on our Prod instance, yet it works on Prod and does not work on Dev, 

 

heres the User configuration

User DN = blank
User object class = user
User object filter = (|(&(objectCategory=Person)(memberOf:1.2.840.113556.1.4.1941:=CN=SEC-HUMANS,OU=Security,OU=Groups,DC=MYCOMPANY,DC=local))(CN=MYCOMPANYApp)(sAMAccountName=jira*)(CN=svn*)(CN=teamcity*))

User Name attribute = sAMAccountName
User name RDN attribute = cn
User first name attribute = givenName
User last name attribute = sn
User display name attribute = displayName
User email attribute = mail
User group attribute = memberOf
User password attribute = unicode Pwd
User unique Identifier = objectGUID

The logs dont show any activity when I "test search", I cant detect why its not able to search the tree. thanks. 

3 answers

I checked debug logs from both instances, only diffrence I can spot is that the nonworking Dev instance is doing a search with this "accountExpires" attribute.  I think this is messing up the search, whats weird is that I dont have that attribute configured anywhere in my settings, its picking it up from somewhere and adding it to the search string.

 

 

with a paging size of: 999
2017-07-12 14:32:22,520 http-bio-127.0.0.1-8095-exec-20 DEBUG [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on baseDN: dc=COMP,dc=local, filter: (&(|(&(objectCategory=Person)(memberOf:1.2.840.113556.1.4.1941:=CN=SEC-HUMANS,OU=Security,OU=Groups,DC=COMP,DC=local))(CN=COApp)(sAMAccountName=jira*)(CN=svn*)(CN=teamcity*))(|(accountExpires=0)(accountExpires>=131443579422920000))) took 0ms

Hi Mike,

From this description it looks like it may be related with this issue https://jira.atlassian.com/browse/CWD-4736 which was fixed in 2.12.0. Could you please check how it behaves when you switch off the 'Filter out expired users' in your directory configuration on your dev instance?

 

Best Regards,

Marcin Kempa

That was it, I unchecked Filter out expired users, did a User Test Search, and its searching. 

Looks like a bug in current version.

 

this is my build

Crowd 2.12.0 Build #751 2017-04-25

Marcin Kempa Atlassian Team Jul 12, 2017

Could you check the accountExpires attribute of some of your users in the Active Directory that should be returned in search but are not? Also would it be possible for you to post some sample LDIFF from your AD instance with dummy data that would illustrate the problem?

This would help us to verify the behaviour.

 

Best Regards,

Marcin Kempa

I cant find that attribute in our AD tree, 

heres a sample user

Untitled.png

 

Also checked our AD user trees, we dont have a "accountExpires" attribute anywhere

Hello, is this something that is part of design or a bug? We need to upgrade our crowd servers but I cant move forward until I know that I can use that Expried USers feature. 

Marcin Kempa Atlassian Team Jul 19, 2017

I think that at this point it would be best to contact Atlassian support. 

In 2.12.0 we've fixed the handling of expired AD accounts in Crowd (https://jira.atlassian.com/browse/CWD-4736). However, with your setup it seems that etiher accountExpires is not present or Crowd does not handle its value correctly.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

230 views 12 14
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you