Table 3-1 Syntaxes support in Directory Server

Syntax

Description

Binary

Indicates that values for this attribute are binary.

Boolean

Indicates that this attribute has one of only two values, true or false.

Country String

Indicates that values for this attribute are limited to exactly two printable string

 

characters; for example, US for the United States.

DN

Indicates that values for this attribute are DNs.

DirectoryString

Indicates that values for this attribute are case-insensitive strings.

GeneralizedTime

Indicates that values for this attribute are encoded as printable strings. The time zone

 

must be specified. It is strongly recommended to use GMT time.

IA5String

Indicates that values for this attribute are case-exact strings.

Integer

Indicates that valid values for this attribute are numbers.

OctetString

Indicates that values for this attribute are binary; this is the same as using the binary

 

syntax.

Postal Address

Indicates that values for this attribute are encoded in the format postal-address

 

=dstring* ("$"dstring). For example:

 

1234 Main St.$Raleigh, NC

 

12345$USA

TelephoneNumber

Indicates that values for this attribute are in the form of telephone numbers. It is

 

recommended to use telephone numbers in international form.

URI

Indicates that the values for this attribute are in the form of a URL, introduced by a

 

string such as http://. The URI has the same behavior as IA5String. See RFC 2396

 

for more information on this syntax.

3.2.3 Standard object classes

Object classes are used to group related information. Typically, an object class represents a real object, such as a person or a fax machine. Before it is possible to use an object class and its attributes in the directory, it must be identified in the schema. The directory recognizes a standard list of object classes by default; these are listed and described in the Directory Server Schema Reference.

Each directory entry belongs to at least one object classes. Placing an object class identified in the schema on an entry tells the Directory Server that the entry can have a certain set of possible attribute values and must have another, usually smaller, set of required attribute values.

Object class definitions contain the following information:

•A unique name.

•An object identifier (OID) that names the object.

•A set of mandatory attributes.

•A set of allowed (or optional) attributes.

For example, the standard person object class appears in the schema as follows:

objectclasses: ( 2.5.6.6 NAME 'person' DESC 'Standard Person Object Class' SUP top

MUST (objectclass $ sn $ cn) MAY (description $ seeAlso $ tele\ phoneNumber $ userPassword)

X-ORIGIN 'RFC 2252' )

As is the case for all the Directory Server's schema, object classes are defined and stored directly in Directory Server. This means that the directory's schema can be both queried and changed with standard LDAP operations.

3.2 Standard schema

29

Page 28 Page 30
Page 29
Image 29
HP UX Direry Server manual Standard object classes, Syntaxes support in Directory Server
Page 28 Page 30

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.
Top Page Image Contents