Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
In our old server environment we have had an search query with this format : (&(sAMAccountName=*)) which has been workin but when we uppgrade to a new server environment the search query above gives an Exception in our loga like this: javax.naming.directory.InvalidSearchFilterException: Unbalanced parenthesis; remaining name
Would be nice to receice some suggestions how to correct the LDAP search query
Hi Thomas, in old version of JIRA and Confluence you had to escape the ampersand symbol and the exclamation mark symbol before adding to your XML file (see here), but in the current versions you can simply use (sAMAccountName=*), which should return the same result.
Hi Thomas, yes that's correct. The equivalent to your old filter in newer versions of JIRA is just (sAMAccountName=*)
Just one additional information, since you're using the attribute sAMAccountName, I assume you're connecting JIRA with AD, is that right?
If so, it may be better use the user filter as (&(objectCategory=Person)(sAMAccountName=*)) otherwise the synchronization may pull other LDAP objects that are not users to your JIRA application.
I hope it helps.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs