Home > Articles > Operating Systems, Server > Solaris

Like this article? We recommend

Solaris 8 OE LDAP Implementation

Technically speaking, the Solaris 8 LDAP implementation is client side only. In theory, because it communicates over the standard LDAP v3 , any v3-compliant directory server should be able to support Solaris 8 OE LDAP clients. In practice, there are several required server features and configuration parameters that need to be set up. Because the set up is rather complex, scripts are available for the Netscape Directory Server 4.1x and Sun ONE Directory Server 5.1 software (formerly known as the iPlanet_ Directory Server). These are the only two directory servers that Sun Microsystems, Inc. supports.

Several design decisions were made in the development of the Solaris 8 OE LDAP Client that affect its implementation. The following sections detail some of these designs to illustrate why so many configuration changes on the directory server are necessary.

LDAP Client Profiles

There are a number of configuration parameters that a Solaris OE LDAP client needs to set before it can communicate with a directory server. Specific parameters include the address of the directory server(s) the client will attempt to get naming service data from and the name of a proxy account to bind to the server.

One approach you can use is to set these parameters in a local file on each client and update them locally. The obvious disadvantage to this approach is that more complex installations and cumbersome updates are required if the configuration parameters need to be changed. Alternatively, you can maintain the configuration data in a central repository, like the directory itself, so it can be easily retrieved during client installation and reconfiguration. This data is stored in client profiles.

Storing client configurations in the directory requires you to create schema definitions that define the object class and attributes that contain the client profile data. This requires the extension of the directory server's schema to include the client profile object class and associated attributes.

Support of RBAC and Projects

Role-based access control (RBAC) and projects that were introduced in the Solaris 8 OE relied on a naming service to operate efficiently. Because the RFC2307 schema did not include object classes and attributes that supported these features, schema extensions are required if you want to use the features with the LDAP Client.

nisdomain Object

The Solaris 8 OE clients have the notion of belonging to a naming service domain. NIS uses this domain name to locate an NIS server that supports the domain the client belongs to. To provide an equivalent, the directory server maintains the name of the domain it serves. Here again, an object class and associated attribute is required, making a schema extension necessary.

proxyagent Account

The Solaris 8 OE access the naming service during the boot process. For example, host names might need to be resolved to IP addresses by applications started in the Solaris 8 OEs run command (rc) scripts. At boot time, a user is not logged in and the OE needs to bind to the directory server as someone. Instead of setting up anonymous access and lessening security, create an account that the client uses during boot time and grant that account the appropriate permissions. Before a client can be initialized using this approach, the account must exist on the server. It must also be assigned a password for use during authentication.

pam_unix Support

The Solaris 8 OE provides two types of authentication methods that use LDAP as a naming service. Both of these are implemented as pluggable authentication modules (PAMs). The first, referred to as pam_unix, uses the traditional Solaris 8 OE method of authentication. This method stores passwords in a one-way hashing format called crypt. When a user logs in, the crypt representation of the password is retrieved from the naming service and compared with the password entered by the user after it is hashed using the same crypt algorithm. With this method, the authentication process takes place on the client and clear-text passwords are never sent over the network.

An issue with pam_unix support is that passwords stored on the server must be readable by someone so they can be retrieved. If the pam_unix style of authentication is deployed with LDAP as the naming service, a proxyagent account is used to retrieve the password. This means that this account must have the proper access rights to search for and retrieve passwords.

The other authentication method, called pam_ldap, performs the authentication on the directory server, so the password is never sent to the client in any form.

Self-Write Access Control

By default, directory servers assume that users should be able to modify the entry they use to bind to the directory. In most cases, this is a reasonable assumption. However, there are certain fields that a Solaris 8 OE user account entry contains that you would not want a user to modify. For example, you would not want users to change their uidNumber attribute to 0, effectively giving them root privileges. Therefore, the default access control instruction (ACI) requires modification.

Virtual List Controls

The virtual list view (VLV) is an extension for the LDAP v3 search operation. This extension is required to avoid overloading the client that makes a search request that returns a very large number of entries. For example, if you executed an ldaplist passwd command and had 10,000 users, 10,000 entries would be returned. Without browsing indexes, the maximum limit on the number of entries a server can return would most likely be exceeded.

Setting Up the Solaris 8 OE LDAP Client and Server Configuration

At the time the Solaris 8 OE was released, Netscape Directory Server 4.16.1 was the directory server version that Sun Microsystems, Inc. supported. This version of directory server software was co-packaged with the Solaris 8 OE media kit and could be downloaded from the Sun ONE/iPlanet Web site. In either case, it was contained in a single compressed tar file. The basic directory server installation steps were:

  1. Uncompress and un-tar the file:

    directory-4.16-domestic-us.sparc-sun-solaris2.6.tar.gz
  2. Run the setup command from the installation directory.

  3. Create an rc startup script to automatically start the directory server at boot time.

Once the directory server was installed, the setup_native_LDAP.sh script, which is available on the http://www.sun.com/blueprints Web site, was run to configure the server to support Solaris 8 OE LDAP Clients. The basic steps the script performed were:

  1. Add the required schema definitions.

  2. Create the directory information tree (DIT) structure.

  3. Create the nisDomain object.

  4. Set up appropriate access controls.

  5. Generate an LDAP Client profile.

  6. Create attribute indexes.

  7. Create VLV indexes.

After the server was configured, you imported your NIS data by either running publicly available NIS migration scripts or by using the dsimport command, which was included in the NIS Extensions software.

When the directory server was configured and populated, you were able to initialize the Solaris 8 OE LDAP Clients. The easiest way to do this was by specifying the client profile that was created by the setup script on the command line when the ldapclient command is run. For example:

# ldapclient -P SolarisNative 192.9.200.1

One additional configuration step was required if you planned to use pam_ldap authentication instead of the default pam_unix. In this case, you also needed to modify the /etc/pam.conf file on the client. For example, you could replace the following lines:

login auth required  /usr/lib/security/$ISA/pam_unix.so.1

with the following lines:

login auth sufficient /usr/lib/security/$ISA/pam_unix.so.1 
login auth required  /usr/lib/security/
$ISA/pam_ldap.so.1 try_first_pass

Additional lines, not shown here, would also need to be modified to allow remote logins and password management functions.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020