3.3 Mapping the data to the default schema

The data identified during the site survey, as described in “Performing a site survey”, must be mapped to the existing default directory schema. This section describes how to view the existing default schema and provides a method for mapping the data to the appropriate existing schema elements.

If there are elements in the schema that do not match the existing default schema, create custom object classes and attributes. See “Customizing the schema” for more information.

3.3.1 Viewing the default directory schema

The default directory schema is stored in /etc/opt/dirsrv/schema.

This directory contains all the common schema for the Directory Server. The LDAPv3 standard user and organization schema can be found in the 00core.ldif file. The configuration schema used by earlier versions of the directory can be found in the 50ns-directory.ldiffile.

CAUTION:

Do not modify the default directory schema.

For more information about each object class and attribute found in directory, see the HP-UX Directory Server schema reference. For more information about the schema files and directory configuration attributes, see the HP-UX Directory Server configuration, command, and file reference.

3.3.2 Matching data to schema elements

The data identified in the site survey now needs to be mapped to the existing directory schema. This process involves the following steps:

1.Identify the type of object the data describes.

Select an object that best matches the data described in the site survey. Sometimes, a piece of data can describe multiple objects. Determine if the difference needs to be noted in the directory schema.

For example, a telephone number can describe an employee's telephone number and a conference room's telephone number. Determine if these different sorts of data need to be considered different objects in the directory schema.

2.Select a similar object class from the default schema.

It is best to use the common object classes, such as groups, people, and organizations.

3.Select a similar attribute from the matching object class.

Select an attribute from within the matching object class that best matches the piece of data identified in the site survey.

4.Identify the unmatched data from the site survey.

If there are some pieces of data that do not match the object classes and attributes defined by the default directory schema, customize the schema. See “Customizing the schema” for more information.

For example, the following table maps directory schema elements to the data identified during the site survey in Chapter 2 “Planning the directory data”:

Table 3-2 Data mapped to default directory schema

Data

Owner

Object Class

Attribute

Employee name

HR

person

cn (commonName)

User password

IS

person

userPassword

30 Designing the directory schema

Page 30
Image 30
HP UX Direry Server manual Mapping the data to the default schema, Viewing the default directory schema

UX Direry Server specifications

HP UX Directory Server is a robust and scalable solution designed for managing directory information within enterprise networks. Developed by Hewlett-Packard (HP), this server offers an extensive set of features tailored to meet the needs of organizations that require an efficient way to store, manage, and retrieve identity and access data.

One of the key features of HP UX Directory Server is its ability to handle large directories with significant volumes of data. Built on a highly optimized architecture, it provides excellent performance and can support millions of entries without sacrificing speed or reliability. This capability makes it an ideal choice for large-scale deployments in enterprises that require high availability and responsiveness.

In addition to its scalability, HP UX Directory Server supports a wide range of protocols, including LDAP (Lightweight Directory Access Protocol), which ensures seamless integration with diverse applications and systems across various platforms. The server maintains standards compliance, which facilitates interoperability and simplifies administration tasks.

Security is a top priority for HP UX Directory Server, offering an array of features to protect sensitive information. It supports secure data transmission via TLS/SSL protocols, ensuring encrypted communication between clients and servers. Advanced access controls allow administrators to define fine-grained permissions, helping to safeguard directory data against unauthorized access.

Another salient feature of HP UX Directory Server is its replication capabilities. The server can replicate directory data across multiple instances, ensuring data consistency and availability in distributed environments. This feature is essential for businesses operating across different geographical locations or requiring failover solutions for disaster recovery.

HP UX Directory Server also comes equipped with tools for data management, including an intuitive administration console for configuring and monitoring the server. Additionally, it offers customizable schema capabilities, enabling organizations to tailor the directory structure to fit their specific needs.

Integration with existing identity management solutions is streamlined through connectors and APIs, allowing organizations to extend their directory services and enhance user experience.

In summary, HP UX Directory Server is a powerful directory management solution that combines scalability, security, and integration flexibility. Its support for industry standards, advanced replication, and comprehensive administrative tools makes it an essential asset for organizations seeking to manage identity and access efficiently. By leveraging this technology, businesses can improve their operational efficiency and ensure a secure and organized approach to directory management.