Configuring the Oracle Directory Server Enterprise Edition on a Trusted Extensions System

The LDAP naming service is the supported naming service for Trusted Extensions. If your site is not yet running the LDAP naming service, configure an Oracle Directory Server Enterprise Edition (Directory Server) on a system that is configured with Trusted Extensions.

If your site is already running a Directory Server, then you need to add the Trusted Extensions databases to the server. To access the Directory Server, you then set up an LDAP proxy on a Trusted Extensions system.

Note - If you do not use this LDAP server as an NFS server or as a server for Sun Ray clients, then you do not need to install any labeled zones on this server.

Collect Information for the Directory Server for LDAP

Determine the values for the following items.

The items are listed in the order of their appearance in the System Install Wizard.

Install Wizard Prompt	Action or Information
Oracle Directory Server Enterprise Edition `version`
Administrator User ID	The default value is `admin`.
Administrator Password	Create a password, such as `admin123`.
Directory Manager DN	The default value is `cn=Directory Manager`.
Directory Manager Password	Create a password, such as `dirmgr89`.
Directory Server Root	The default value is `/var/Sun/mps`. This path is also used later if the proxy software is installed.
Server Identifier	The default value is the local system.
Server Port	If you plan to use the Directory Server to provide standard LDAP naming services to client systems, use the default value, `389`. If you plan to use the Directory Server to support a subsequent installation of a proxy server, enter a nonstandard port, such as `10389`.
Suffix	Include your domain component, as in `dc=example-domain,dc=com`.
Administration Domain	Construct to correspond to the Suffix, as in, `example-domain.com`.
System User	The default value is `root`.
System Group	The default value is `root`.
Data Storage Location	The default value is `Store configuration data on this server`.
Data Storage Location	The default value is `Store user data and group data on this server`.
Administration Port	The default value is the Server Port. A suggested convention for changing the default is `software-version` times `1000`. For software version `5.2`, this convention would result in port `5200`.

Install the Oracle Directory Server Enterprise Edition

The Directory Server packages are available from the Oracle web site for Sun Software Products.

Before You Begin

You are on a Trusted Extensions system with a global zone. The system has no labeled zones. You must be in the root role in the global zone.

Trusted Extensions LDAP servers are configured for clients that use pam_unix to authenticate to the LDAP repository. With pam_unix, the password operations, and therefore the password policy, are determined by the client. Specifically, the policy set by the LDAP server is not used. For the password parameters that you can set on the client, see Managing Password Information in Oracle Solaris 11.1 Administration: Security Services. For information about pam_unix, see the pam.conf(4) man page.

Note - The use of pam_ldap on an LDAP client is not an evaluated configuration for Trusted Extensions.

Before you install the Directory Server packages, add the FQDN to your system's hostname entry.
The FQDN is the Fully Qualified Domain Name. This name is a combination of the host name and the administration domain, as in:
```
## /etc/hosts
...
192.168.5.5 myhost myhost.example-domain.com
```
Download the Oracle Directory Server Enterprise Edition packages from the Oracle web site for Sun Software Products.
Select the most recent software that is appropriate for your platform.
Install the Directory Server packages.
Answer the questions by using the information from Collect Information for the Directory Server for LDAP. For a full list of questions, defaults, and suggested answers, see Chapter 11, Setting Up Oracle Directory Server Enterprise Edition With LDAP Clients (Tasks), in Oracle Solaris Administration: Naming and Directory Services and Chapter 12, Setting Up LDAP Clients (Tasks), in Oracle Solaris Administration: Naming and Directory Services.

(Optional) Add the environment variables for the Directory Server to your path.

# $PATH
/usr/sbin:.../opt/SUNWdsee/dsee6/bin:/opt/SUNWdsee/dscc6/bin:/opt/SUNWdsee/ds6/bin:
/opt/SUNWdsee/dps6/bin

(Optional) Add the Directory Server man pages to your MANPATH.
```
/opt/SUNWdsee/dsee6/man
```

Enable the cacaoadm program and verify that the program is enabled.

# /usr/sbin/cacaoadm enable
# /usr/sbin/cacaoadm start
start: server (pid n) already running

Ensure that the Directory Server starts at every boot.
Templates for the SMF services for the Directory Server are in the Oracle Directory Server Enterprise Edition packages.
- For a Trusted Extensions Directory Server, enable the service.
```
# dsadm stop /export/home/ds/instances/your-instance
# dsadm enable-service -T SMF /export/home/ds/instances/your-instance
# dsadm start /export/home/ds/instances/your-instance
```
  For information about the dsadm command, see the dsadm(1M) man page.
- For a proxy Directory Server, enable the service.
```
# dpadm stop /export/home/ds/instances/your-instance
# dpadm enable-service -T SMF /export/home/ds/instances/your-instance
# dpadm start /export/home/ds/instances/your-instance
```
  For information about the dpadm command, see the dpadm(1M) man page.

Verify your installation.

# dsadm info /export/home/ds/instances/your-instance
Instance Path:         /export/home/ds/instances/your-instance
Owner:                 root(root)
Non-secure port:       389
Secure port:           636
Bit format:            32-bit
State:                 Running
Server PID:            298
DSCC url:              -
SMF application name:  ds--export-home-ds-instances-your-instance
Instance version:      D-A00

Troubleshooting

For strategies to solve LDAP configuration problems, see Chapter 13, LDAP Troubleshooting (Reference), in Oracle Solaris Administration: Naming and Directory Services.

Create an LDAP Client for the Directory Server

You use this client to populate your Directory Server for LDAP. You must perform this task before you populate the Directory Server.

You can create the client temporarily on the Trusted Extensions Directory Server, then remove the client on the server, or you can create an independent client.

Before You Begin

You are in the root role in the global zone.

Add Trusted Extensions software to a system.
You can use the Trusted Extensions Directory Server, or add Trusted Extensions to a separate system.

On the client, configure LDAP in the name-service/switch service.

Display the current configuration.

# svccfg -s name-service/switch listprop config
config                       application
config/value_authorization   astring       solaris.smf.value.name-service.switch
config/default               astring       "files ldap"
config/host                  astring       "files dns"
config/netgroup              astring       ldap
config/printer               astring       "user files ldap"

Change the following property from the default:

# svccfg -s name-service/switch setprop config/host = astring: "files ldap dns"

In the global zone, run the ldapclient init command.

In this example, the LDAP client is in the example-domain.com domain. The server's IP address is 192.168.5.5.

# ldapclient init -a domainName=example-domain.com -a profileName=default \
> -a proxyDN=cn=proxyagent,ou=profile,dc=example-domain,dc=com \
> -a proxyDN=cn=proxyPassword={NS1}ecc423aad0 192.168.5.5
System successfully configured

Set the server's enableShadowUpdate parameter to TRUE.
```
# ldapclient -v mod -a enableShadowUpdate=TRUE \
> -a adminDN=cn=admin,ou=profile,dc=example-domain,dc=com
System successfully configured
```
For information about the enableShadowUpdate parameter, see enableShadowUpdate Switch in Oracle Solaris Administration: Naming and Directory Services and the ldapclient(1M) man page.

Configure the Logs for the Oracle Directory Server Enterprise Edition

This procedure configures three types of logs: access logs, audit logs, and error logs. The following default settings are not changed:

All logs are enabled and buffered.
Logs are placed in the appropriate /export/home/ds/instances/your-instance/logs/LOG_TYPE directory.
Events are logged at log level 256.
Logs are protected with 600 file permissions.
Access logs are rotated daily.
Error logs are rotated weekly.

The settings in this procedure meet the following requirements:

Audit logs are rotated daily.
Log files that are older than 3 months expire.
All log files use a maximum of 20,000 MBytes of disk space.
A maximum of 100 log files is kept, and each file is at most 500 MBytes.
The oldest logs are deleted if less than 500 MBytes free disk space is available.
Additional information is collected in the error logs.

Before You Begin

You must be in the root role in the global zone.

Configure the access logs.

The LOG_TYPE for access is ACCESS. The syntax for configuring logs is the following:

dsconf set-log-prop LOG_TYPE property:value

# dsconf set-log-prop ACCESS max-age:3M
# dsconf set-log-prop ACCESS max-disk-space-size:20000M
# dsconf set-log-prop ACCESS max-file-count:100
# dsconf set-log-prop ACCESS max-size:500M
# dsconf set-log-prop ACCESS min-free-disk-space:500M

Configure the audit logs.

# dsconf set-log-prop AUDIT max-age:3M
# dsconf set-log-prop AUDIT max-disk-space-size:20000M
# dsconf set-log-prop AUDIT max-file-count:100
# dsconf set-log-prop AUDIT max-size:500M
# dsconf set-log-prop AUDIT min-free-disk-space:500M
# dsconf set-log-prop AUDIT rotation-interval:1d

By default, the rotation interval for audit logs is one week.

Configure the error logs.

In this configuration, you specify additional data to be collected in the error log.

# dsconf set-log-prop ERROR max-age:3M
# dsconf set-log-prop ERROR max-disk-space-size:20000M
# dsconf set-log-prop ERROR max-file-count:30
# dsconf set-log-prop ERROR max-size:500M
# dsconf set-log-prop ERROR min-free-disk-space:500M
# dsconf set-log-prop ERROR verbose-enabled:on

(Optional) Further configure the logs.
You can also configure the following settings for each log:
```
# dsconf set-log-prop LOG_TYPE rotation-min-file-size:undefined
# dsconf set-log-prop LOG_TYPE rotation-time:undefined
```
For information about the dsconf command, see the dsconf(1M) man page.

Configure a Multilevel Port for the Oracle Directory Server Enterprise Edition

To work in Trusted Extensions, the server port of the Directory Server must be configured as a multilevel port (MLP) in the global zone.

Before You Begin

You must be in the root role in the global zone.

Start the txzonemgr.
```
# /usr/sbin/txzonemgr &
```
Add a multilevel port for the TCP protocol to the global zone.
The port number is 389.
Add a multilevel port for the UDP protocol to the global zone.
The port number is 389.

Populate the Oracle Directory Server Enterprise Edition

Several LDAP databases have been created or modified to hold Trusted Extensions data about label configuration, users, and remote systems. In this procedure, you populate the Directory Server databases with Trusted Extensions information.

Before You Begin

You must be in the root role in the global zone. You are on an LDAP client where shadow updating is enabled. For the prerequisites, see Create an LDAP Client for the Directory Server.

Create a staging area for files that you plan to use to populate the naming service databases.
```
# mkdir -p /setup/files
```

Copy the sample /etc files into the staging area.

# cd /etc
# cp aliases group networks netmasks protocols /setup/files
# cp rpc services auto_master /setup/files

# cd /etc/security/tsol
# cp tnrhdb tnrhtp /setup/files

Caution - Do not copy the *attr files. Rather, use the -S ldap option to the commands that add users, roles, and rights profiles to the LDAP repository. These commands add entries for the user_attr, auth_attr, exec_attr, and prof_attr databases. For more information, see the user_attr(4) and useradd(1M) man pages.

Remove the +auto_master entry from the /setup/files/auto_master file.

Create the zone automaps in the staging area.

# cp /zone/public/root/etc/auto_home_public /setup/files
# cp /zone/internal/root/etc/auto_home_internal /setup/files
# cp /zone/needtoknow/root/etc/auto_home_needtoknow /setup/files
# cp /zone/restricted/root/etc/auto_home_restricted /setup/files

In the following list of automaps, the first of each pair of lines shows the name of the file. The second line of each pair shows the file contents. The zone names identify labels from the default label_encodings file that is included with the Trusted Extensions software.

Substitute your zone names for the zone names in these lines.
myNFSserver identifies the NFS server for the home directories.

/setup/files/auto_home_public
 * myNFSserver_FQDN:/zone/public/root/export/home/&

/setup/files/auto_home_internal
 * myNFSserver_FQDN:/zone/internal/root/export/home/&

/setup/files/auto_home_needtoknow
 * myNFSserver_FQDN:/zone/needtoknow/root/export/home/&

/setup/files/auto_home_restricted
 * myNFSserver_FQDN:/zone/restricted/root/export/home/&

Use the ldapaddent command to populate the Directory Server with every file in the staging area.
For example, the following command populates the server from the hosts file in the staging area.
```
# /usr/sbin/ldapaddent -D "cn=directory manager" \
-w dirmgr123 -a simple -f /setup/files/hosts hosts
```
If you ran the ldapclient command on the Trusted Extensions Directory Server, disable the client on that system.
In the global zone, run the ldapclient uninit command. Use verbose output to verify that the system is no longer an LDAP client.
```
# ldapclient -v uninit
```
For more information, see the ldapclient(1M) man page.
To populate the Trusted Extensions network databases in LDAP, use the tncfg command with the -S ldap option.
For instructions, see Labeling Hosts and Networks (Tasks).

Skip Navigation Links
Exit Print View
	Trusted Extensions Configuration and Administration Oracle Solaris 11.1 Information Library