title: Why not always use (objectClass=*) in the LDAP search filter?
body: <p>I created the following filter for search users in Active Directory:</p>
  <pre><code>(&amp;(objectClass=*)(|(sAMAccountName=u)(userPrincipalName=u)) 
  </code></pre>
  <p>It is possible to create more qualified filter:</p>
  <pre><code>(&amp;(objectClass=person)(|(sAMAccountName=u)(userPrincipalName=u)) 
  </code></pre>
  <p>The question is why?</p>
  <p>What benefits of using specified class <code>person</code>?</p>
  <p>Is it possible that the same directory contain object where <code>objectClass</code> is not <code>person</code> but the following is true <code>(|(sAMAccountName=u)(userPrincipalName=u))</code>?</p>
  <p>Why not always use <code>(objectClass=*)</code> in the LDAP search filter?</p>