2 Planning the directory data

The data stored in the directory may include user names, email addresses, telephone numbers, and information about groups users are in, or it may contain other types of information. The type of data in the directory determines how the directory is structured, who is given access to the data, and how this access is requested and granted.

This chapter describes the issues and strategies behind planning the directory's data.

2.1 Introduction to directory data

Some types of data are better suited to the directory than others. Ideal data for a directory has some of the following characteristics:

It is read more often than written.

It is expressible in attribute-data format (for example, surname=jensen).

It is of interest to more than one person or group. For example, an employee's name or the physical location of a printer can be of interest to many people and applications.

It will be accessed from more than one physical location.

For example, an employee's preference settings for a software application may not seem to be appropriate for the directory because only a single instance of the application needs access to the information. However, if the application is capable of reading preferences from the directory and users might want to interact with the application according to their preferences from different sites, then it is very useful to include the preference information in the directory.

2.1.1 Information to include in the directory

Any descriptive or useful information about a person or asset can be added to an entry as an attribute. For example:

Contact information, such as telephone numbers, physical addresses, and email addresses.

Descriptive information, such as an employee number, job title, manager or administrator identification, and job-related interests.

Organization contact information, such as a telephone number, physical address, administrator identification, and business description.

Device information, such as a printer's physical location, type of printer, and the number of pages per minute that the printer can produce.

Contact and billing information for a corporation's trading partners, clients, and customers.

Contract information, such as the customer's name, due dates, job description, and pricing information.

Individual software preferences or software configuration information.

Resource sites, such as pointers to web servers or the file system of a certain file or application.

Using the Directory Server for more than just server administration requires planning what other types of information to store in the directory. For example:

Contract or client account details

Payroll data

Physical device information

Home contact information

Office contact information for the various sites within the enterprise

2.1.2Information to exclude from the directory

HP-UX Directory Server is excellent for managing large quantities of data that client applications read and write, but it is not designed to handle large, unstructured objects, such as images or

2.1 Introduction to directory data

17

Page 17
Image 17
HP UX Direry Server Planning the directory data, Introduction to directory data, Information to include in the directory

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.