Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend

System Configuration

The system configuration procedures are:

  • "Following the Midframe Article" on page 7

  • "Creating the wcappKeyStore" on page 8

  • "Installing the FM Public Key In the wcappKeyStore" on page 11

  • "Installing the wcapp Public Key In the fmKeystore" on page 14

  • "Configuring wcapp To Use SSL" on page 15

Following the Midframe Article

To build a secure Sun Fire Link network, follow the recommendations of the "Building Secure Sun Fire Link Interconnect Networks Using Midframe Servers" article at: http://www.sun.com/solutions/blueprints/0203/817-1656.pdf.

If you are building a direct-connect topology, an MSP is not required. However, you still must set up the FM's proxy on each domain to use SSL for communication between it and the FM. If you do not deploy an MSP, you must select the machine where the FM resides with caution.

Creating the wcappKeyStore

"Building Secure Sun Fire Link Interconnect Networks Using Midframe Servers" discusses the motivation and technology behind SSL. For an overview of SSL and public key cryptography, refer to that article.

Two keystores were created: the FM Proxy keystore and the FM keystore. In this article, an additional keystore and another key to the FM keystore are created. FIGURE 4 shows where the certificate (public key) and private keys are distributed.

Figure 4FIGURE 4 Public and Private Key Locations

To Create the wcappKeyStore

  1. Create the keystore and generate the key pair by typing the following command in a safe private directory on the MSP.

  2. NOTE

    You must type this command as a single line. Multiple lines are used in the examples for legibility purposes only. Press return for the fmkey password.

    # /usr/bin/keytool -genkey -dname "cn=CommonName, ou=OrganizationName,
     o=CompanyName, s=SN c=US" -alias wcappKey -keystore 
    wcappKeyStore -validity 180
    Enter keystore password: YourPassword
    Enter key password for fmKey: Password
        (RETURN if same as keystore password): 

    The preceding command creates the keystore named fmKeyStore in the working directory, and assigns it the password YourPassword. Substitute a password for YourPassword. This password must be kept secret to the administrators. This password is referred to as the keystore password. You must remember this password because it is used in other steps.

    The italicized items in the preceding command represent a value and the keywords are abbreviations for the following:

TABLE 1 X.500 Distinguished Names

KeyWord

X.500 Distinguished Names

Example

cn

CommonName (Name of person)

John Smith

ou

OrganizationUnit (department)

Purchasing

on

OrganizationName (company)

ABC Systems, Inc.

ln

LocalityName (city name)

Burlington

s

Statement (state)

MA

c

Country

US


The distinguished names are used to identify entities, such as those named by the subject and issuer.

CAUTION

Keytool generates a public and private key pair for the entity fmkeys. The generated key expires in 180 days. Every 180 days you must generate a new private and public key and replace the private key on the proxy and public key on the FM.

  1. Verify that the keystore was correctly created and the key entry is contained in the keystore.

  2. Substitute your password for the keystore password you specified in the previous command.

    # keytool -list -keystore wcappKeyStore
    Enter keystore password: YourPassword
    
    Keystore type: jks
    Keystore provider: SUN
    
    Your keystore contains 1 entry:
    
    wcappkeys, Fri Apr 11 12:11:44 EDT 2003, keyEntry,
    Certificate fingerprint (MD5): 
    F1:11:FF:90:B0:D8:C6:DE:23:CE:36:3F:81:B2:30:36

    The MD5 fingerprint and date will be will be different than those shown.

  3. Generate a file that contains the certificate (public key) for the wcapp key.

  4. This public key will be installed in the fmKeyStore.

    # /usr/bin/keytool -export -alias wcappKey
     -keystore wcappKeyStore > wcAppCert
    Enter keystore password: YourPassword
  5. Verify that the public key was created:

  6. # /usr/bin/keytool -printcert -file wcAppCert
    Owner: CN=CommonName, OU=OrganizationName,
     O=CompanyName, ST="SN c=US"
    Issuer: CN=CommonName,ls -OU=OrganizationName,
     O=CompanyName, ST="SN c=US"
    Serial number: 3cb70740
    Valid from: Fri Apr 11 12:11:44 EDT 2003 
    until: Thus Oct 09 12:11:44 EDT 2003
    Certificate fingerprints:
         MD5: F1:11:FF:90:B0:D8:C6:DE:23:CE:36:3F:81:B2:30:36
         SHA1: 6C:76:5D:E9:64:84:08:E2:95:0B:64:95:70:6D:3F:E9:
         F5:D5:87:7E
    

    Assume that the strings for CommonName and the other keywords are what you entered in the -genkey keytool in Step 1. The certificate fingerprint and date should be the same as that displayed when the fmKeyStore was listed in Step 2.

Installing the FM Public Key In the wcappKeyStore

For the wcapp program to authenticate the SSL connection between the FM and wcapp the FM public key must be placed in the wcappKeyStore. First you must extract the public key from the FM keystore. For the following command to work, you must have followed the instructions in the article "Building Secure Sun Fire Link Interconnect Networks Using Midframe Servers."

To Install the FM Public Key in the wcappKeyStore

  1. Generate a file that contains the certificate (public key) for the proxyKey.

  2. This public key will be installed in the fmKeyStore.

    # /usr/bin/keytool -export -alias fmKey -keystore 
    /opt/SUNWwcfm/classes/fmKeyStore > fmCert

    Enter keystore password: YourPassword

  3. Verify that the public key was created.

  4. # /usr/bin/keytool -printcert -file fmCert
    Owner: CN=CommonName, OU=OrganizationName, 
    O=CompanyName, ST="SN c=US"
    Issuer: CN=CommonName,ls -OU=OrganizationName, 
    O=CompanyName, ST="SN c=US"
    Serial number: 3cb70740
    Valid from: Fri Apr 11 12:15:44 EDT 2003 until: 
    Thus Oct 09 12:11:44 EDT 2003
    Certificate fingerprints:
    MD5: F2:11:FF:90:B0:D8:C6:DE:23:CE:36:3F:81:B2:30:36
    SHA1: 6C:76:5D:E9:64:84:08:E2:95:0B:64:95:70:6D:3F:
    E9:F5:D5:87:7E

    Assume that the strings for CommonName and the other keywords are what you entered in the -genkey keytool in Step 1"Creating the wcappKeyStore" on page 8.

  5. Import the FM public key into wcappKeyStore:

  6. # /usr/bin/keytool -import -file fmCert 
    -keystore wcappKeyStore
    Enter keystore password: YourPassword
    Owner: CN=CommonName, OU=OrganizationName, 
    O=CompanyName, ST="SN c=US"
    Issuer: CN=CommonName, OU=OrganizationName, 
    O=CompanyName, ST="SN c=US"
    Valid from: Fri Apr 11 12:11:44 EDT 2003 until: 
    Thus Oct 09 12:11:44 EDT 2003
    Certificate fingerprints:
    MD5: F1:11:FF:90:B0:D8:C6:DE:23:CE:36:3F:81:B2:30:36 
    SHA1:6C:76:5D:E9:64:84:08:E2:95:0B:64:95:70:6D:
    3F:E9:F5:D5:87:7
    Trust this certificate? [no]: yes
    Certificate was added to keystore
  7. Validate that wcappKeyStore contains the private key for the proxy and the public key for the F:

  8. # /usr/bin/keytool -list -keystore wcappKeyStore
    keystore password: YourPassword
    Keystore type: jks
    Keystore provider: SUN
    Your keystore contains 2 entries:
    wcapp Key, Fri Apr 11 12:15:44 EDT 2003 
    Certificate fingerprints(MD5) F2:11:FF:90:B0:D8:C6:
    DE:23:CE:36:3F:81:B2:30:36
    fmkey, Fri Apr 11 12:11:44 EDT 2003 trustedCertEntry,
    Certificate fingerprint (MD5):
    F1:11:FF:90:B0:D8:C6:DE:23:CE:36:3F:81:B2:30:36

Installing the wcapp Public Key In the fmKeystore

To Install the wcapp public key In the fmKeyStore

  1. Type the following command to install the fmKeyStore.

  2. The fmKeyStore needs a public key for the wcapp key pair.

    # /usr/bin/keytool -import -file wcappCert
     -keystore fmKeyStore
    Enter keystore password: YourPassword
    Owner: CN=CommonName, OU=OrganizationName, 
    O=CompanyName, ST="SN c=US"
    Serial Number:84848484
    Issuer: CN=CommonName, OU=OrganizationName, 
    O=CompanyName, ST="SN c=US"
    Valid from: Fri Apr 11 12:15:44 EDT 2003 until: 
    Thus Oct 09 12:11:44 EDT 2003
    Certificate fingerprints:
    MD5: F2:11:FF:90:B0:D8:C6:DE:23:CE:36:3F:81:B2:30:36 
    SHA1:6C:76:5D:E9:64:84:08:E2:95:0B:64:95:70:6D:
    3F:E9:F5:D5:87:7
    Trust this certificate? [no]: yes
    Certificate was added to keystore
  3. Validate that wcappKeyStore contains the private key for the private key for the proxy and public key for the FM:

  4. # /usr/bin/keytool -list -alias -keystore 
    /opt/SUNWwcfm/classes/fmKeyStore
    keystore password: YourPassword
    Keystore type: jks
    Keystore provider: SUN
    Your keystore contains 2 entries:
    fmKey, Fri Apr 11 12:11:44 EDT 2003 
    Certificate fingerprints(MD5) F1:11:FF:90:B0:D8:C6:DE:23
    :CE:36:3F:81:B2:30:36
    wcappKey, Fri Apr 11 12:15:44 EDT 2003 trustedCertEntry,
    Certificate fingerprint (MD5):
    F2:11:FF:90:B0:D8:C6:DE:23:CE:36:3F:81:B2:30:36

Configuring wcapp To Use SSL

These steps must be performed on every SC (both the primary and the backup) in your configuration. For example, if you have two Sun Fire 15K or Sun Fire 12K systems you must repeat the following installation steps on all four SCs:

  • "To Configure wcapp Java Virtual Machine to use SSL" on page 15

  • "To Install the wcappKeyStore" on page 17

  • "To Create the ssl.info File" on page 18

  • "To Stop and Restart wcapp" on page 18

To Configure wcapp Java Virtual Machine to use SSL

  1. Download the Java™ Secure Socket Extension (JSSE) 1.0.3 program.

  2. You can download the file to any location on your local disk. Note that JSSE 1.0.3 requires that you have Java 1.2.1 or greater already installed. You can download the file from:

    http://java.sun.com/products. 
    The file name is jsse-1_0_3-do.zip.
  3. Uncompress and extract the downloaded file by typing the following command to unzip the download.

  4. This will create a directory named jsse1.0.2, with two subdirectories named doc and lib. The following command will unzip the download:

    # unzip jsse-1_0_3-do.zip
    Archive: jsse-1_0_3-do.zip
     inflating: jsse1.0.3/BUGS.html   
     inflating: jsse1.0.3/CHANGES.txt  
     inflating: jsse1.0.3/COPYRIGHT.ht
    ... Many more files are listed
  5. The JSSE lib subdirectory contains the extension files jsse.jar, jcert.jar and jnet.jar. Copy these files into the /usr/java1.2/lib/ext (installed extension) directory:

  6. # cp lib/jsse.jar JRE/lib/ext/jsse.jar
    # cp lib/jcert.jar JRE/lib/ext/jcert.jar
    # cp lib/jnet.jar JRE/lib/ext/jnet.jar
  7. Verify that the files exist and they are owned by root.

  8. # ls -l $JRE/lib/ext
    -rw-r--r--  1 root   root 7637 Feb 20 10:17 jcert.jar
    -rw-r--r--  1 root   root 3098 Feb 20 10:17 jnet.jar
    -rw-r--r--  1 root   root 463471 Feb 20 10:17 jsse.jar
  9. Register the Sun JSSE provider.

  10. The standard JSSE comes with a cryptographic service provider (provider for short) named SunJSSE. Although the SunJSSE provider must be configured explicitly, this provider should be registered statically. The registration is done by editing the security properties file, which is located at:

    JRE/lib/security/java.security.

    One of the types of properties contained in the java.security file is of the following form:

    security.provider.n=providerClassName

    This line declares the security provider and its preference.

  11. Add a new line to that section and install the standard provider shipped with the Java run-time environment (JRE).

  12. The entries should now look like:

    security.provider.1=sun.security.provider.Sun
    security.provider.2=com.sun.net.ssl.internal.ssl.Provider

To Install the wcappKeyStore

The previously created keystore (wcappKeyStore) must be distributed to each SC domain. To move the key, it is recommended that you use an encrypted file, that is, scp, to copy the file onto your system.

  1. Execute the following command.

  2. Substitute the machine name of MSP for the server that is acting as your MSP.

    # scp MSP:/privatedir/wcappKeyStore 
    /opt/SUNWSMS/SMS1.3/classes/wcappKeyStore
  3. Verify that this file is root read only.

  4. It is important to protect private key.

    # ls -l /opt/SUNWSMS/SMS1.3/wcappKeyStore
    -rw-------  1 root   root 7637 Feb 20 10:17
     /opt/SUNWSMS/SMS1.3/classes/wcappKeyStore
  5. Edit the java.policy file so that the proxy has access to the fmKeyStore file.

  6. Add the following lines above the }; in the policy file. The wcapp java.policy file is located in: /opt/SUNWSMS/SMS1.3/classes/com/sun/wildcat/common/server.policy

    permission java.io.FilePermission 
    "/opt/SUNWSMS/SMS1.3/classes/wcappKeyStore", "read"; 
    permission java.io.FilePermission 
    " /opt/SUNWSMS/SMS1.3/classes/ssl.info", "read";

To Create the ssl.info File

The ssl.info file contains the information that wcapp needs to use the SSL.

  1. Create a file called file /opt/SUNWSMS/SMS1.3/classes/ssl.info containing the following lines.

  2. Substitute the KeyStore password for YourPassword.

    KEY_STORE_PASSPHRASE=YourPassword
    KEY_STORE_LOCATION=/opt/SUNWSMS/SMS1.3/classes/wcappKeyStore
  3. Verify that the file is root read only.

  4. This information is sensitive. Access to the file should be restricted to root. The following command will verify the access to the file:

    # ls -l /opt/SUNWSMS/SMS1.3/classes/ssl.info 
    -rw-------  1 root   root 7637 Feb 20 10:17 
    /opt/SUNWSMS/SMS1.3/classes/ssl.info

To Stop and Restart wcapp

To make wcapp use SSL and the enhanced security settings, you must stop and restart wcapp by stopping and restarting the entire SMS. If failover is enabled, the SC will failover when SMS is stopped so failover should be disabled and one SC modified and tested before you define the other SC as main. Modify and test the SC before you re-enable failover.

  1. Type the following command to stop the proxy:

  2. # /etc/init.d/sms stop
  3. Type the following command to restart wcapp.

  4. # /etc/inid.d/sms start 
  5. Verify that wcapp restarted with enhanced security.

  6. Only the critical lines of output are listed. The rest are ignored for readability.

    # tail /tmp/scapout.out 
    .
    .
    .
    using SSL.
    .
    .
    .
  7. Repeat Steps 1 through 3 for each SC.

  • + Share This
  • 🔖 Save To Your Account

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