17.Restart the Directory Server. The server must be restarted from the command line.

/opt/dirsrv/slapd-example/restart-slapd

When the server restarts, it prompts for the PIN or password to unlock the key database. This is the same password used when the server certificate and key were imported into the database.

Using a pin.txt file to store the token database passwords allows the Directory Server to restart without prompting for the password. This is covered in “Creating a password file for the Directory Server”.

18.Restart the Administration Server. The server must be restarted from the command line.

/opt/dirsrv/sbin/restart-ds-admin

When the server restarts, it prompts for the PIN or password to unlock the key database. This is the same password used when the server certificate and key were imported into the database.

Using a password.conf file to store the token database passwords allows the Administration Server to restart without prompting for the password. This is covered in “Creating a password file for the Administration Server”.

NOTE:

After configuring SSL/TLS for the Administration Server, be certain that the address reads https when next logging into the Administration Server or Directory Console. With SSL/TLS, all connections to the Administration Server must be over HTTPS. Otherwise, the operation will time out, unable to find the server since it is running on a secure connection. After successfully connecting, a dialog box appears to accept the certificate. Click OK to accept the certificate (either only for that current session or permanently).

6.4 Creating password files

If SSL/TLS is enabled for the Directory Server or Administration Server, the server prompts for a password to access the certificate and key databases every time the server is restarted. The servers can restart silently if that password is supplied in a password file which the start scripts can access.

6.4.1 Creating a password file for the Directory Server

It is possible to store the certificate password in a password file. By placing the certificate database password in a file, the server can be started from the Directory Server Console and also restarted automatically when running unattended.

CAUTION:

This password is stored in clear text within the password file, so its usage represents a significant security risk. Do not use a password file if the server is running in an unsecured environment.

The password file must be in the same directory where the other key and certificate databases for Directory Server are stored. This is usually the main configuration directory, /etc/opt/dirsrv/slapd-instance_name. The file should be named pin.txt.

Include the token name and password in the file. For example:

Internal (Software) Token:secret

For the NSS software crypto module (the default software database), the token is always called internal.

The PIN file should be owned by the Directory Server user and set to read-only by the Directory Server user, with no access to anyone other user (mode 0400).

76 Using SSL/TLS with the Console

Page 75 Page 77
Page 76
Image 76
HP UX Direry Server manual Creating password files, Creating a password file for the Directory Server
Page 75 Page 77

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