rilpoint_mw113

LDAP - Domain Server

Line 14: Line 14:
→ Apache web server integrated with the LDAP server for centralized user authentication
→ Apache web server integrated with the LDAP server for centralized user authentication
-
II  Directory structure
+
 
 +
[[File:LDAP1.ppm]]
 +
 
 +
 
 +
==II  Directory structure==
An LDAP database stores information on objects in a hierarchical manner. Objects have attributes that contain the information that is stored about the object. Objects also have classes that define which attributes must and may be stored on the object. Objects in an LDAP database are distinguished by their Distinguished Name (DN) which indicates their place in the hierarchical tree.  
An LDAP database stores information on objects in a hierarchical manner. Objects have attributes that contain the information that is stored about the object. Objects also have classes that define which attributes must and may be stored on the object. Objects in an LDAP database are distinguished by their Distinguished Name (DN) which indicates their place in the hierarchical tree.  
The protocol accesses LDAP directories are based on X.500 model
The protocol accesses LDAP directories are based on X.500 model
Line 38: Line 42:
"dn" is the distinguished name of the entry; it's neither an attribute nor a part of the entry. "cn=Ravi Shankar" is the entry's RDN (Relative Distinguished Name), and "dc=example,dc=com" is the DN of the parent entry, where "dc" denotes 'Domain Component'. The other lines show the attributes in the entry. Attribute names are typically mnemonic strings, like "cn" for common name, "dc" for domain component, "mail" for e-mail address and "sn" for surname. A server holds a subtree starting from a specific entry, e.g. "dc=example,dc=com" and its children.  
"dn" is the distinguished name of the entry; it's neither an attribute nor a part of the entry. "cn=Ravi Shankar" is the entry's RDN (Relative Distinguished Name), and "dc=example,dc=com" is the DN of the parent entry, where "dc" denotes 'Domain Component'. The other lines show the attributes in the entry. Attribute names are typically mnemonic strings, like "cn" for common name, "dc" for domain component, "mail" for e-mail address and "sn" for surname. A server holds a subtree starting from a specific entry, e.g. "dc=example,dc=com" and its children.  
-
III  LDAP Server Configuration
+
==III  LDAP Server Configuration==
The below detail shows the configuration details of the LDAP server
The below detail shows the configuration details of the LDAP server
Line 51: Line 55:
# ping ldapserver.cdacchennai.in
# ping ldapserver.cdacchennai.in
-
 
+
[[File:LDAP2.jpg]]
The following configuration setting shows the LDAP server authentication with the BOSS client  system.  
The following configuration setting shows the LDAP server authentication with the BOSS client  system.  
-
 
+
==1. Installing the LDAP server Packages==
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
 
+
-
1. Installing the LDAP server Packages
+
Below are the steps to setup a LDAP Server on BOSS Server.
Below are the steps to setup a LDAP Server on BOSS Server.
Line 176: Line 169:
-
2. Add New Directory to the Domain dc=cdacchennai,dc=in
+
==2. Add New Directory to the Domain dc=cdacchennai,dc=in==
Create the file base.ldif
Create the file base.ldif
Line 336: Line 329:
-
5. Deleting user or group in LDAP Directory
+
==5. Deleting user or group in LDAP Directory==
ldapdelete -x -W -D 'cn=admin,dc=cdacchennai,dc=in'  "uid=user1, ou=people, dc=cdacchennai,dc=in"
ldapdelete -x -W -D 'cn=admin,dc=cdacchennai,dc=in'  "uid=user1, ou=people, dc=cdacchennai,dc=in"
Line 354: Line 347:
-
IV  LDAP Client in BOSS Client machine
+
==IV  LDAP Client in BOSS Client machine==
Test the LDAP server
Test the LDAP server
Line 374: Line 367:
-
1.  Configuring LDAP Client
+
==1.  Configuring LDAP Client==
Install the following packages
Install the following packages
Line 451: Line 444:
shutdown -r now
shutdown -r now
-
2.  Login into the Client Machine
+
==2.  Login into the Client Machine==
Now login as a LDAP user which is available in the LDAP server in the login screen of the client machine.  
Now login as a LDAP user which is available in the LDAP server in the login screen of the client machine.  

Revision as of 06:57, 2 February 2012