Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When the client successfully BINDs, the server has indicated to the client that the username and its associated password are correct - the server is able to verify that the password matches what was supplied in the BIND request. That is all that happens. If the BIND is unsuccessful, then the username and/or password is not correct. There is no distinction between LDAP objects at this point.</p> <p>What is needed is a way for the client to determine of what type <code>username</code> is. There are at least two reasonable ways to do this:</p> <ul> <li>The LDAP object has an attribute indicating which user type.</li> <li>The LDAP object is a member of a group (in this case, admin or normal).</li> </ul> <p>The group method is more flexible than the attribute method, since new "normal" users or new "admin" users can simply be added to the appropriate group.</p> <p>For example, an admin group:</p> <pre><code>cn=admin users,ou=groups,o=example.com objectClass: groupOfNames member: cn=admin user 1,ou=groups,o=example.com member: cn=admin user 2,ou=groups,o=example.com </code></pre> <p>or a normal user group:</p> <pre><code>cn=normal users,ou=people,o=example.com objectClass: groupOfNames member: cn=normal user 1,ou=groups,o=example.com member: cn=normal user 2,ou=groups,o=example.com member: cn=normal user 3,ou=groups,o=example.com </code></pre> <p>The client can determine to which group the <code>username</code> by searching using the appropriate search request parameters. If the <code>username</code> belongs to an admin group, then display <code>homescreen.php</code> else <code>homescreen2.php</code>.</p> <p>These are two possibilities. There may be other ways, depending on your setup and the type of server (although LDAP clients must never be written as if they know what type of server they are connected to).</p> <h3>see also</h3> <ul> <li><a href="http://www.ldapguru.info/ldap/mastering-ldap-search-filters.html" rel="nofollow">LDAP: Mastering Search Filters</a></li> <li><a href="http://www.ldapguru.info/ldap/ldap-search-best-practices.html" rel="nofollow">LDAP: Search best practices</a></li> <li><a href="http://www.ldapguru.info/ldap/ldap-programming-practices.html" rel="nofollow">LDAP: Programming practices</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow to filter user in LDAP PHP
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTerry Gardner
    1. USTerry Gardner
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThanks for your guidance. But I am confused here. Can I put two group (admin and normal user ) in one page of coding ? Then, when someone is try to login, they will be brought to respected home page according to their group which I set earlier. It this possible ?
      singulars
      1. PO
      1. USuser2810332
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload