title: Issue with LDAP and posixAccount vs posixaccount
body: <p>Recently had an issue in an environment where we use ldap to update our system with groups / users. The LDAP system is not in our control, we can only run queries against it, and done within our code. The LDAP is part of the orgs single-sign on. The UI for this was upgraded and LDAP apparently untouched. Our system has a ldap member criteria that was set to &quot;user, posixAccount&quot; and &quot;hard-coded&quot;, so not easy to change. Things stopped working and eventually identified that if we changed the case to posixaccount, things returned back to normal.</p>
  <p>It's an absolute mystery how something that has worked for years suddenly stops working because from our side it was expecting posixAccount and not posixaccount, and we're told the upgrade didn't touch LDAP side of things.</p>
  <p>Any ideas of what could've changed to have this effect?</p>
  <p>(We are unable to get any info on the LDAP system or what was actually done. We can use ldapsearch for example which actually doesn't worry about the case and understand that it should be case insensitive, but that's secondary for now).</p>