Directory Service Overview What can a directory do? Finding Things Managing Things Lightweight Database Applications Security Applications Why we use Directory Extensibility Distribution scale Replication scale Performance LDAP(Lightweight Directory Access Protocol) OLTP(On-Line Transaction Process) Standards
Directory Service Overview ◼ What can a Directory do? ◼ Finding Things ◼ Managing Things ◼ Lightweight Database Applications ◼ Security Applications ◼ Why we use Directory ◼ Extensibility ◼ Distribution scale ◼ Replication scale ◼ Performance ◼ LDAP(Lightweight Directory Access Protocol ) ◼ OLTP(On-Line Transaction Process) ◼ Standards
Naming convention Every name is generated by a set of syntactic rules called a naming convention An atomic name is an indivisible component of a name. as defined by the naming convention a compound name represents a sequence of zero or more atomic names composed according to the naming convention
Naming Convention ◼ Every name is generated by a set of syntactic rules called a naming convention. ◼ An atomic name is an indivisible component of a name, as defined by the naming convention. ◼ A compound name represents a sequence of zero or more atomic names composed according to the naming convention
Naming convention The UN pathname ■From1 eft to right, is seperated by’/ /usr/hello, for example, names a file hello in the file directory usr, which is located in the root of the file system a The dms naming convention From right to left, is seperated by ." Thus the dNs name sales. Wiz. CoM names a DNS entry with the name sales, relative to the DNs entry wiz. COM. The DNs entry Wiz. COM, in turn, names an entry with the name Wiz in the com entry
Naming Convention ◼ The UNIX pathname： ◼ From left to right，is seperated by ’/’ ： /usr/hello, for example, names a file hello in the file directory usr, which is located in the root of the file system. ◼ The DNS naming convention ： ◼ From right to left，is seperated by ".". Thus the DNS name sales.Wiz.COM names a DNS entry with the name sales, relative to the DNS entry Wiz.COM. The DNS entry Wiz.COM, in turn, names an entry with the name Wiz in the COM entry
Naming convention Lightweight Directory Access ProtOcOl (LDAP): From left to right, is seperated by,, and takes the form of name=value The ldaP name cn=Rosanna lee 0=Sun, c=US names an LDAP entry cn=Rosanna lee relative to the entry o=Sun, which in turn, is relative to c=us. LDAP store the data in a form of a tree Bindings The association of an atomic name with an object is called a binding. for example: a file name is bound to a file; The DNS contains bindings that map machine names to IP addresses An LDAP name is bound to an ldap entry
Naming Convention ◼ Lightweight Directory Access Protocol (LDAP)： ◼ From left to right，is seperated by’ , ’ ，and takes the form of name=value。The LDAP name cn=Rosanna Lee, o=Sun, c=US names an LDAP entry cn=Rosanna Lee, relative to the entry o=Sun, which in turn, is relative to c=us. ◼ LDAP store the data in a form of a tree ◼ Bindings ◼ The association of an atomic name with an object is called a binding. for example：a file name is bound to a file；The DNS contains bindings that map machine names to IP addresses. An LDAP name is bound to an LDAP entry
Naming convention a References and addresses For the objects that cant be stored directly into directory, it needs to find the object by address and then get the content and the status of the object context: a a set ofname-to-object bindings Can be further divided to root context and sub contexto A name in one context object can be bound to another context object(called a subcontext)that has the same naming convention A context provides a lookup (resolution)operation that returns the object and may provide operations such as those for binding names, unbinding names, and listing bound names
Naming Convention ◼ References and Addresses ◼ For the objects that can’t be stored directly into directory, it needs to find the object by address and then get the content and the status of the object. ◼ context: ◼ a set of name-to-object bindings ◼ Can be further divided to root context and sub context。 A name in one context object can be bound to another context object (called a subcontext) that has the same naming convention ◼ A context provides a lookup (resolution)operation that returns the object and may provide operations such as those for binding names, unbinding names, and listing bound names