Solaris Operating System

Naming & Directory Services Technical FAQ

Technical Questions


Q:
What new functionality has been introduced in Solaris 9 Operating System (OS) with regard to naming and directory services?
A:
There are several new features introduced in naming services in the Solaris platform. The three most notable are:
  • Secure LDAP Client
  • NIS+ to LDAP Migration tools
  • Sun ONE Directory Server 5.1 Integration (formerly iPlanet Directory Server)

Back to Top


Q:
What is the Secure LDAP client?
A:
Solaris 8 native LDAP authentication did not offer any session or password encryption, which matched the Sun ONE Directory Server's encrypted authentication algorithms. In the Solaris 9 OS, SASL/Digest-MD5 and SSL/TLS 1.0 have been added to allow for password or complete session encryption respectively. This allows a high degree of assurance in using LDAP as a naming service.

Back to Top


Q:
What additional functionality has been incorporated in the "Secure LDAP client" for Solaris 9 software?
A:
The Solaris 9 LDAP client supports schema mapping and uses a standardized configuration profile. In addition, the Solaris 9 LDAP client is completely backward compatible with the Solaris 8 client. New commands like ldapaddent for more sophisticated LDAP add entry and Idsconfig for more sophisticated configuration utility for the Sun ONE Directory Server 5.1 have been incorporated.

Back to Top


Q:
What is the status of NIS+ for the Solaris 9 Operating System?
A:
NIS+ is a mature and stable naming service. Sun's customers have indicated a preference for using IETF standards for naming services based on "LDAP". Sun is indicating formally, that there are plans for NIS+ to be removed after the Solaris 9 release. Customers are encouraged to migrate to the Sun ONE Directory Server v5.1, which is integrated in the Solaris 9 platform. The Sun ONE Directory Server incorporates the latest technology and is based on LDAP standards. For more detailed information on what the EOF announcement means to you visit www.sun.com/directory/nisplus/transition.html.

Back to Top


Q:
What migration tools have been provided to help migration from NIS+ to LDAP environments?
A:
The Solaris 9 OS includes NIS+ to LDAP migration tools to help migrate NIS+ environments to LDAP. Migration is a two-step process:
  • Data & Server Migration
  • Client migration
    1. Data migration is made possible through the synchronization tools in the product that move data from NIS+ server to the LDAP server.
    2. Client migration is more cumbersome of the two steps since the number of clients involved is large. The client migration thus can only be done in a phased manner. The migration tool allows the NIS+ clients to co-exist with the LDAP server and transparently communicate with the LDAP server. . The migrati on tool sits as gateway and talks NIS+ on the front-end and ypldapd at the backend.
For more information on migration from NIS+ to LDAP refer to "NIS+ to LDAP" White paper.

Back to Top


Q:
What is the future plan for NIS?
A:
Through products and services, Sun is enabling customers to make the transition to LDAP based naming services. Once these transitions are well underway, Sun will evaluate the appropriate time to formally announce the transition plan for NIS. It is likely that our plan will follow the one for NIS+, modified by experiences gained during that transition. The earliest that such an announcement would occur would be after the next major release following the Solaris 9 OS.

Back to Top


Q:
What does the integration of the Sun ONE Directory Server mean to customers?
A:
The integration means that the Sun ONE Directory Server will now be part of the Solaris 9 OS and will support the Solaris package format. In addition, the installation of the directory server will be part of the Solaris installation process thus providing for a smoother installation experience. It is Sun's stated strategic direction to use the directory as the central system repository for various manageability and security functionality that will deliver better service levels at lower service costs.

Back to Top


Q:
What are the features of the Sun ONE Directory Server?
A:
The Solaris 9 OS will include the Sun ONE Directory Server 5.1 with a 200,000-user entry license for the enterprise. Based on a highly advanced, carrier-grade architecture, Sun ONE Directory Server 5.1 delivers a high performance, highly scalable, user-management infrastructure that helps organizations manage identity, relationships, and risk. The directory server incorporates several unique features like multi-master replication, chaining, multiple database backend support and DIGEST-MD5 support which allow for improved reliability and scalability. In addition, features like IPv6 support and documented plug-in API along with roles and class of services provide for better manageability and ease of administration. For more details on what the directory can do for your network identity infrastructure please visit /software/products/directory_srvr/home_directory.xml.

Back to Top


Q:
What are limitations of the 200,000-entry license?
A:
The license allows for full-production usage of the Sun ONE Directory Server 5.1 up to 200,000 entries. An entry is defined as a single unique Distinguished Name ("DN") and its contained attributes. Excluded are all necessary objects to support a Solaris user such as NIS/NIS+ tables. The 200,000 entries per enterprise network can be used for either intranet or extranet applications. Thus an entry in essence is defined as one that uses the LDAP store for authentication. System management entries like printers, hosts etc. that are not authentication types of entries are not counted towards the 200,000 entries limit.

Back to Top


Q:
What is the mechanics of accounting entries on the master and the replica; do the entries on the replica count towards the 200,000-entry limit?
A:
Only "DN" type entries on the master are considered towards the 200,000-entry limit. Customers can deploy as many replica servers at no charge as long as they are also on the Solaris 9 OS. Any combination of Solaris 9 software and another operating system-NT, Linux, AIX etc.- a license must be purchased to cover the users on the other operating system.

Example Deployment # 1
A customer with the following deployment configuration with deployment of both master and replica on Solaris 9
  • A customer with the following deployment configuration with deployment of both master and replica on Solaris 9
  • Server B Master = 25,000 with single unique "DN's"
  • Server C Master = 125000 with single unique "DN's"
  • Server C Replica = 125000 with single unique "DN's"
  • Total enterprise wide entries = 200000
No additional license needs to be purchased beyond the 200000-entry license included in Solaris.

Example Deployment # 2
A customer has the following deployment scenario of both master and replica
  • Solaris 8 Master = 150000 with single unique "DN's"
  • HP-UX Slave = 50000 with single unique "DN's"
  • IBM-AIX- Slave = 50000 with single unique "DN's"
  • Windows-NT Slave = 50000 with single unique "DN's"
Customers have to pay for the 150000 entries on the slaves since those entries are not on Solaris but on HP-UX. AIX and NT. The license allows for usage of the 200000 entries only in a Solaris deployment i.e. both master and slave have to be on Solaris 9.

Example Deployment # 3
A customer with the following deployment configuration for entries in the iPla net directory server (LDAP) data store
  • Server A Master = 50000 with single unique DN's
  • Server B Master = 150000 with single unique DN's
  • Printer Entries = 2000 entries
  • Host entries = 1000 entries
  • NIS maps = 40
  • NIS+ maps = 50
  • Total enterprise wide entries = 200000
Entries towards system management like printers, hosts, NIS tables etc. are not "DN" type entries and therefore don't count towards the 200000-entry limit.

Back to Top


Q:
We are currently using the iPlanet Directory Server 4.16, what is the process for upgrading to the latest version of the Sun ONE Directory Server?
A:
There is couple of ways one could upgrade to using the latest version of the Sun ONE Directory Server. One way is to upgrade to the version of Solaris that has the integrated directory in it. If one however wishes to upgrade on an existing Solaris environment one needs to purchase a support contract for the iPlanet directory Server. The support contract enables upgrade from existing versions of the directory server to newer versions of the directory within the terms as defined in the support contract. Please consult with your Sun sales representative on the exact terms of the support contract.

Back to Top


Q:
How is the Sun ONE Directory Server supported? Is the support for the directory part of the overall Solaris software support plan?
A:
Support for the directory server is provided at an additional charge that is based on the number of entries to be supported. Once the support has been purchased it enables you to upgrade to the latest version of the directory at no additional charge. Please ask your Sun sales representative for additional details.

Back to Top