JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Trusted Extensions Configuration and Administration     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

Part I Initial Configuration of Trusted Extensions

1.  Security Planning for Trusted Extensions

2.  Configuration Roadmap for Trusted Extensions

3.  Adding the Trusted Extensions Feature to Oracle Solaris (Tasks)

4.  Configuring Trusted Extensions (Tasks)

5.  Configuring LDAP for Trusted Extensions (Tasks)

Configuring LDAP on a Trusted Extensions Network (Task Map)

Configuring an LDAP Proxy Server on a Trusted Extensions System (Task Map)

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

Collect Information for the Directory Server for LDAP

Install the Oracle Directory Server Enterprise Edition

Create an LDAP Client for the Directory Server

Configure the Logs for the Oracle Directory Server Enterprise Edition

Configure a Multilevel Port for the Oracle Directory Server Enterprise Edition

Populate the Oracle Directory Server Enterprise Edition

Creating a Trusted Extensions Proxy for an Existing Oracle Directory Server Enterprise Edition

Create an LDAP Proxy Server

Creating a Trusted Extensions LDAP Client

Make the Global Zone an LDAP Client in Trusted Extensions

Part II Administration of Trusted Extensions

6.  Trusted Extensions Administration Concepts

7.  Trusted Extensions Administration Tools

8.  Security Requirements on a Trusted Extensions System (Overview)

9.  Performing Common Tasks in Trusted Extensions

10.  Users, Rights, and Roles in Trusted Extensions (Overview)

11.  Managing Users, Rights, and Roles in Trusted Extensions (Tasks)

12.  Remote Administration in Trusted Extensions (Tasks)

13.  Managing Zones in Trusted Extensions

14.  Managing and Mounting Files in Trusted Extensions

15.  Trusted Networking (Overview)

16.  Managing Networks in Trusted Extensions (Tasks)

17.  Trusted Extensions and LDAP (Overview)

18.  Multilevel Mail in Trusted Extensions (Overview)

19.  Managing Labeled Printing (Tasks)

20.  Devices in Trusted Extensions (Overview)

21.  Managing Devices for Trusted Extensions (Tasks)

22.  Trusted Extensions Auditing (Overview)

23.  Software Management in Trusted Extensions

A.  Site Security Policy

Creating and Managing a Security Policy

Site Security Policy and Trusted Extensions

Computer Security Recommendations

Physical Security Recommendations

Personnel Security Recommendations

Common Security Violations

Additional Security References

B.  Configuration Checklist for Trusted Extensions

Checklist for Configuring Trusted Extensions

C.  Quick Reference to Trusted Extensions Administration

Administrative Interfaces in Trusted Extensions

Oracle Solaris Interfaces Extended by Trusted Extensions

Tighter Security Defaults in Trusted Extensions

Limited Options in Trusted Extensions

D.  List of Trusted Extensions Man Pages

Trusted Extensions Man Pages in Alphabetical Order

Oracle Solaris Man Pages That Are Modified by Trusted Extensions

Glossary

Index

Creating a Trusted Extensions LDAP Client

The following procedure creates an LDAP client for an existing Trusted Extensions Directory Server.

Make the Global Zone an LDAP Client in Trusted Extensions

This procedure establishes the LDAP naming service configuration for the global zone on an LDAP client.

Use the txzonemgr script.


Note - If you plan to set up a name server in each labeled zone, you are responsible for establishing the LDAP client connection to each labeled zone.


Before You Begin

The Oracle Directory Server Enterprise Edition, that is, the Directory Server, must exist. The server must be populated with Trusted Extensions databases, and this client system must be able to contact the server. So, the Directory Server must have assigned a security template to this client. A specific assignment is not required, a wildcard assignment is sufficient.

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

  1. If you are using DNS, add dns to the name-service/switch configuration.

    The standard naming service switch file for LDAP is too restrictive for Trusted Extensions.

    1. 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/netgroup              astring       ldap
      config/printer               astring       "user files ldap"
    2. Add dns to the host property and refresh the service.
      # svccfg -s name-service/switch setprop config/host = astring: "files dns ldap"
      # svccfg -s name-service/switch:default refresh
    3. Verify the new 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 ldap
      config/netgroup              astring       ldap
      config/printer               astring       "user files ldap"

      The Trusted Extensions databases use the default configuration files ldap, so are not listed.

  2. To create an LDAP client, run the txzonemgr command without any options.
    # txzonemgr &
    1. Double-click the global zone.
    2. Select Create LDAP Client.
    3. Answer the following prompts and click OK after each answer:
      Enter Domain Name:                   Type the domain name
      Enter Hostname of LDAP Server:       Type the name of the server
      Enter IP Address of LDAP Server servername: Type the IP address
      Enter LDAP Proxy Password:       Type the password to the server
      Confirm LDAP Proxy Password:     Retype the password to the server
      Enter LDAP Profile Name:         Type the profile name
    4. Confirm or cancel the displayed values.
      Proceed to create LDAP Client?

      When you confirm, the txzonemgr script runs the ldapclient init command.

  3. Complete client configuration by enabling shadow updates.
    # ldapclient -v mod -a enableShadowUpdate=TRUE \
    > -a adminDN=cn=admin,ou=profile,dc=domain,dc=suffix
    System successfully configured
  4. Verify that the information on the server is correct.
    1. Open a terminal window, and query the LDAP server.
      # ldapclient list

      The output looks similar to the following:

      NS_LDAP_FILE_VERSION= 2.0
      NS_LDAP_BINDDN= cn=proxyagent,ou=profile,dc=domain-name
      ...
      NS_LDAP_BIND_TIME= number
    2. Correct any errors.

      If you get an error, redo Step 2 through Step 4. For example, the following error can indicate that the system does not have an entry on the LDAP server:

      LDAP ERROR (91): Can't connect to the LDAP server.
      Failed to find defaultSearchBase for domain domain-name

      To correct this error, you need to check the LDAP server.