Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java System Access Manager 6 2005Q1 Administration Guide 

Chapter 3
Configuring Access Manager in SSL Mode

Using Secure Socket Layer (SSL) with simple authentication guarantees confidentiality and data integrity. To enable Access Manager in SSL, mode you would typically:

  1. Configure Access Manager with a secure web container
  2. Configure Access Manager to a secure Directory Server

The following sections describe these steps:

Configuring Access Manager With a Secure Sun Java System Web Server

To configure Access Manager in SSL mode with Sun Java System Web Server, see the following steps:

  1. In the Access Manager console, go to the Service Configuration module and select the Platform service. In the Server List attribute, remove the http:// protocol, and add the https:// protocol. Click Save.

    2. Note

    Be sure to click Save. If you don’t, you will still be able to proceed with the following steps, but all configuration changes you have made will be lost and you will not be able to log in as administrator to fix it.

Step 2 through Step 25 describe the Sun Java System Web Server.

  1. Log on to the Web Server console. The default port is 58888.
  2. Select the Web Server instance on which Access Manager is running, and click Manage.

    3. This displays a pop-up window explaining that the configuration has changed. Click OK.

  3. Click on the Apply button located top right corner of the screen.
  4. Click Apply Settings.

    5. The Web Server should automatically restart. Click OK to continue.

  5. Stop the select Web Server instance.
  6. Click the Security Tab.
  7. Click on Create Database.
  8. Enter the new database password and click OK.

    9. Ensure that you write down the database password for later use.

  9. Once the Certificate Database has been created, click on Request a Certificate.
  10. Enter the data in the fields provided in the screen.

    11. The Key Pair Field Password field is the same as you entered in Step 9. In the location field, you will need to spell out the location completely. Abbreviations, such as CA, will not work. All of the fields must be defined. In the Common Name field, provide the hostname of your Web Server.

  11. Once the form is submitted, you will see a message such as:

    12. --BEGIN CERTIFICATE REQUEST---

    afajsdllwqeroisdaoi234rlkqwelkasjlasnvdknbslajowijalsdkjfalsdflasdf

    alsfjawoeirjoi2ejowdnlkswnvnwofijwoeijfwiepwerfoiqeroijeprwpfrwl

    --END CERTIFICATE REQUEST--

  12. Copy this text and submit it for the certificate request.

    13. Ensure that you get the Root CA certificate.

  13. You will receive a certificate response containing the certificate, such as:

    14. --BEGIN CERTIFICATE---

    afajsdllwqeroisdaoi234rlkqwelkasjlasnvdknbslajowijalsdkjfalsdflasdf

    alsfjawoeirjoi2ejowdnlkswnvnwofijwoeijfwiepwerfoiqeroijeprwpfrwl

    --END CERTIFICATE---

  14. Copy this text into your clipboard, or save the text into a file.
  15. Go to the Web Server console and click on Install Certificate.
  16. Click on Certificate for this Server.
  17. Enter the Certificate Database password in the Key Pair File Password field.
  18. Paste the certificate into the provided text field, or check the radio button and enter the filename in the text box. Click Submit.

    19. The browser will display the certificate, and provide a button to add the certificate.

  19. Click Install Certificate.
  20. Click Certificate for Trusted Certificate Authority.
  21. Install the Root CA Certificate in the same manner described in Step 16 through Step 21.
  22. Once you have completed installing both certificates, click on the Preferences tab in the Web Server console.
  23. Select Add Listen Socket if you wish to have SSL enabled on a different port. Then, select Edit Listen Socket.
  24. Change the security status from Disabled to Enabled, and click OK to submit the changes.

Step 26 through Step 28 describe Access Manager.

  1. Open the AMConfig.properties file. By default, the location of this file is etc/opt/SUNWam/config.
  2. Replace all of the protocol occurrences of http:// to https://, except for the Web Server Instance Directory. This is also specified in AMConfig.properties, but must remain the same.
  3. Save the AMConfig.properties file.
  4. In the Web Server console, click the ON/OFF button for the Access Manager hosting web server instance.

    5. The Web Server displays a text box in the Start/Stop page.

  5. Enter the Certificate Database password in the text field and select Start.

Configuring Access Manager with a Secure Sun Java System Application Server

Setting up Access Manager to run on an SSL-enabled Sun Java System Application server is a two-step process. First, secure the Application Server instance to the installed Access Manager, then configure Access Manager itself.

Setting Up Application Server 6.2 With SSL

To Secure the Application Server Instance:

  1. Log into the Sun Java System Application Server console as an administrator by entering the following address in your browser:

    2. http://fullservername:port

    The default port is 4848.

  2. Enter the username and password you entered during installation.
  3. Select the Application Server instance on which you installed (or will install) Access Manager. The right frame displays that the configuration has changed.
  4. Click Apply Changes.
  5. Click Restart. The Application Server should automatically restart.
  6. In the left frame, click Security.
  7. Click the Manage Database tab.
  8. Click Create Database, if it is not selected.
  9. Enter the new database password and confirm, then click the OK button. Make sure that you write down the database password for later use.
  10. Once the Certificate Database has been created, click the Certificate Management tab.
  11. Click the Request link, if it is not selected.
  12. Enter the following Request data for the certificate
    1. Select it if this is a new certificate or a certificate renewal. Many certificates expire after a specific period of time and some certificate authorities (CA) will automatically send you renewal notification.
    2. Specify the way in which you want to submit the request for the certificate.

      3. If the CA expects to receive the request in an E-mail message, check CA E-mail and enter the E-mail address of the CA. For a list of CAs, click List of Available Certificate Authorities.

      If you are requesting the certificate from an internal CA that is using the Sun Java System Certificate Server, click CA URL and enter the URL for the Certificate Server. This URL should point to the certificate server's program that handles certificate requests.

    3. Enter the password for your key-pair file (this is the password you specified in Step 9).
    4. Enter the following identification information:

      5. Common Name. The full name of the server including the port number.

      Requestor Name. The name of the requestor.

      Telephone Number. The telephone number of the requestor

      Common Name. The fully qualified name of the Sun Java System Application Server on which the digital certificate will be installed.

      E-mail Address. The E-mail address of the administrator.

      Organization Name. The name of your organization. The certificate authority may require any host names entered in this attribute belong to a domain registered to this organization.

      Organizational Unit Name. The name of your division, department, or other operational unit of your organization.

      Locality Name (city). The name of your city or town.

      State Name. The name of the state or province in which your organization operates if your organization is in the United States or Canada, respectively. Do not abbreviate.

      Country Code. The two-letter ISO code for your country. For example, the code for the United States is US.

  13. Click the OK button. A message will be displayed, for example:

    14. --BEGIN NEW CERTIFICATE REQUEST---

    afajsdllwqeroisdaoi234rlkqwelkasjlasnvdknbslajowijalsdkjfalsdfla

    alsfjawoeirjoi2ejowdnlkswnvnwofijwoeijfwiepwerfoiqeroijeprwpfrwl

    --END NEW CERTIFICATE REQUEST--

  14. Copy all of this text to a file and click OK. Make sure that you get the Root CA certificate.
  15. Select a CA and follow the instructions on that authority's web site to get a digital certificate. You can get the certificate from CMS, Verisign or Entrust.net
  16. After you receive your digital certificate from the certificate authority, you can copy the text into your clipboard, or save the text into a file.
  17. Go to the Sun Java System Application Server console and click on the Install link.
  18. Select Certificate For This Server.
  19. Enter the Certificate Database password in the Key Pair File Password field. (It is the same password you entered in Step 9).
  20. Paste the certificate into the provided text field, Message text (with headers), or enter the filename in the Message that is in this file text box. Select the appropriate radio button.
  21. Click OK button. The browser displays the certificate, and provides a button to add the certificate.
  22. Click Add Server Certificate.
  23. Install the Root CA Certificate in the same manner described in Step 10 through Step Step 22. However, in Step 18, select Certificate for Trusted Certificate Authority.
  24. Once you have completed installing both certificates, expand the HTTP Server node in the left frame
  25. Select HTTP Listeners under HTTP Server.
  26. Select http-listener-1. The browser displays the socket information.
  27. Change the value of the port used by http-listener-1 from the value entered while installing application server, to a more appropriate value such as 443.
  28. Select SSL/TLS Enabled.
  29. Select Certificate Nickname.
  30. Specify the Return server. This should match the common name specified in Step 12.
  31. Click Save.
  32. Select the Application Server instance on which you will install the Sun Java System Access Manager software. The right frame shows that the configuration has changed.
  33. Click Apply Changes.
  34. Click Restart. The application server should automatically restart.

Setting Up Application Server 8.1 With SSL

To Secure the Application Server Instance:

  1. Make sure that the Application Server instance is stopped.
  2. Change the token password by using the asadmin>change-master-password command.
  3. Go to the Application Server console and select Configuration>HTTP Service>HTTP Listeners.
  4. Click the listener that you wish to enable and in the right pane, select Security:Enabled.
  5. Check if certutil is installed.
    1. Go to /usr/sfw/bin.
    2. If it is not, install the SUNWtlsu package from the following directory:
    3. The shell environment variable, LD_LIBRARY_PATH

      4. LD_LIBRARY_PATH has to have /usr/lib/mps/secv1

  6. Use certutil to check for installed certificates in certdb:
    1. Go to /var/opt/SUNWappserver/domains/domain1/config
    2. certutil -L -d
    3. You will see following output:

      Certificate Name Trust

      Attributes

      Server-Cert u,u,u

      s1as u,u,u

      AM TrustCA CT,CT,CT

      verisignc1g1 T,T,T

      verisignc1g2 T,T,T

      verisignc1g3 T,T,T

      verisignc2g1 T,T,T

      verisignc2g2 T,T,T

      verisignc2g3 T,T,T

      verisignc3g1 T,T,T

      verisignc3g2 T,T,T

      verisignc3g3 T,T,T

      verisignsecureserver T,T,T

      p Valid peer

      P Trusted peer (implies p)

      c Valid CA

      T Trusted CA to issue client certs (implies c)

      C Trusted CA to certs(only server certs for ssl) (implies c)

      u User cert

      w Send warning

      4. Application Server 8.1 installs self signed server certificate (nickname, s1as) in install time and uses it for ssl enabled ports 4848, 8181.

  7. Generate the certificate request.The syntax to do so is:

    8. certutil -R -s subj -o cert-request-file [-d certdir] [-P dbprefix] [-p phone] [-a]

    For example:

    certutil -R -s "CN=test.company1.com, O=company1.com, C=US" -o cert.req -d . -a

  8. Retrieve the certificate from the CA and istall it by using the following command:

    9. certutil -A -n cert-name -t trustargs [-d certdir] [-P dbprefix] [-a] [-i input]

  9. Save server certificate in a file, for example cert.txt.
  10. Install the server certificate with the following command:

    11. certutil -A -n “AMTrustCA” -t “CT<CT,CT” -d. -a -i cert.txt

  11. List the certdb to ensure successful installation. Enter the following command:

    12. /var/opt/SUNWappserver/domains/domain1/config/% certutil -L -d

  12. Go to the Application Server Admin Console and choose HTTP Listeners.

    13. Under General Settings, configure the HTTP Listener with the new server certificate.

  13. Restart the Application Server.

Configuring Access Manager in SSL Mode Using JSS

To configure Access Manager in SSL mode using JSS (Network Security Service for Java):

  1. In the Access Manager console, go to the Service Configuration module and select the Platform service. In the Server List attribute, add the same URL with the HTTPS protocol and an SSL-enabled port number. Click Save.

    2. Note

    If a single instance of Access Manager is listening on two ports (one in HTTP and one in HTTPS) and you try to access Access Manager with a stalled cookie, Access Manager will become unresponsive. This is not a supported configuration.

  2. Open the AMConfig.properties file from the following default location:

    3. /etc/opt/SUNWam/config.

  3. Replace all of the protocol occurrences of http:// to https:// and change the port number to an SSL-enabled port number.
  4. Save the AMConfig.properties file.
  5. Restart the Application Server.

Configuring AMSDK with a Secure BEA WebLogic Server

The BEA WebLogic Server must first be installed and configured as a web container before you configure it with the AMSDK in SSL. For installation instructions, see the BEA WebLogic server documentation. To configure WebLogic as a web container for Access Manager, see Chapter 1, "Access Manager 2005Q1 Configuration Scripts".

To configure a secure WebLogic instance:

  1. Create a domain using the quick start menu
  2. Go to the WebLogic installation directory and generate the certificate request.
  3. Apply for the server certificate using the vetri_csr.txt CSR to a CA
  4. Save the approved certificate in to a text file. For example, approvedcert.txt.
  5. Load the Root CA in cacerts by using the following commands:

    6. cd jdk141_03/jre/lib/security/

    jdk141_03/jre/bin/keytool -keystore cacerts -keyalg RSA -import -trustcacerts -alias "Greenday CA" -storepass changeit -file /opt/bea81/cacert.txt

  6. Load the Server certificate by using the following command:

    7. jdk141_03/jre/bin/keytool -import -keystore keystore -keyalg RSA -import -trustcacerts -file approvedcert.txt -alias "mykey"

  7. Login to WebLogic console with your username and password.
  8. Browse to the following location:

    9. yourdomain> Servers> myserver> Configure Keystores

  9. Select Custom Identity and then Java Standard Trust
  10. Enter the keystore location. For example, /opt/bea81/keystore.
  11. Enter Keystore Password and Keystore Pass Phrase. For example:

    12. Keystore Password: JKS/Java Standard Trust (for WL 8.1 it is only JKS)

    Key Store Pass Phrase: changeit

  12. Review the SSL Private Key Settings Private Key alias and password.

    13. Note

    You must use the full strength SSL licence or SSL startup will fail

  13. In Access Manager, the following parameters in AmConfig.properties are automatically configured during installation. If they are not, you can edit them appropriately:

    14. com.sun.identity.jss.donotInstallAtHighestPriority=true [ this is not required for AM 6.3 and above]

    com.iplanet.security.SecureRandomFactoryImpl=com.iplanet.am.util.Secure RandomFactoryImpl

    com.iplanet.security.SSLSocketFactoryImpl=netscape.ldap.factory.JSSESoc ketFactory

    com.iplanet.security.encryptor=com.iplanet.services.util.JCEEncryption2

    If your JDK path is the following:

    com.iplanet.am.jdk.path=/usr/jdk/entsys-j2se

    then use the keytool utility to import the root CA in the certificate database. For example:

    /usr/jdk/entsys-j2se/jre/lib/security

    /usr/jdk/entsys-j2se/jre/bin/keytool -keystore cacerts -keyalg RSA -import -trustcacerts -alias "machinename" -storepass changeit -file

    /opt/bea81/cacert.txt

    The keytool utility is located in the following directory:

    /usr/jdk/entsys-j2se/jre/bin/keytool

  14. Remove -D"java.protocol.handler.pkgs=com.iplanet.services.comm" from the Access Manager amadmin command line utility.
  15. Configure Access Manager in SSL Mode. For more information, see Configuring Access Manager in SSL Mode Using JSS.

Configuring AMSDK with a Secure IBM WebSphere Application Server

The IBM WebShpere Server must first be installed and configured as a web container before you configure it with the AMSDK in SSL. For installation instructions, see the WebSphere server documentation. To configure WebLogic as a web container for Access Manager, see Chapter 1, "Access Manager 2005Q1 Configuration Scripts".

To configure a secure WebSphere instance:

  1. Start ikeyman.sh, located in the Websphere /bin directory.
  2. From the Signer menu, import the certification authority’s (CA) certificate.
  3. From the Personal Certs menu, generate the CSR.
  4. Retrieve the certificate created in the previous step.
  5. Select Personal Certificates and import the server certificate.
  6. From the WebSphere console, change the default SSL settings and select the ciphers.
  7. Set the default IBMJSSE SSL provider.
  8. Enter the following command to import the Root CA certificate from the file you just created into application server JVM Keystore:

    9. $ appserver_root-dir/java/bin/ keytool -import -trustcacerts -alias cmscacert -keystore ../jre/lib/security/cacerts -file /full_path_cacert_filename.txt

    app-server-root-dir is the root directory for the application server and full_path_cacert_filename.txt is the full path to the file containing the certificate.

  9. In Access Manager, update the following parameters in AmConfig.properties to use JSSE:

    10. com.sun.identity.jss.donotInstallAtHighestPriority=true

    com.iplanet.security.SecureRandomFactoryImpl=com.iplanet.am.util.SecureRan domFactoryImpl

    com.iplanet.security.SSLSocketFactorImpl=netscape.ldap.factory.JSSESocketF actory

    com.iplanet.security.encyptor=com.iplanet.services.unil.JCEEncryption

  10. Configure Access Manager in SSL Mode. For more information, see Configuring Access Manager in SSL Mode Using JSS.

Configuring Access Manager to Directory Server in SSL Mode

To provide secure communications over the network, Access Manager includes the LDAPS communications protocol. LDAPS is the standard LDAP protocol, but it runs on top of the Secure Sockets Layer (SSL). In order to enable SSL communication, you must first configure the Directory Server in SSL mode and then connect Access Manager to Directory Server. The basic steps are as follows:

  1. Obtain and install a certificate for your Directory Server, and configure the Directory Server to trust the certification authority’s (CA) certificate.
  2. Turn on SSL in your directory.
  3. Configure the authentication, policy and platform services to connect to an SSL-enabled Directory Server.
  4. Configure Access Manager to securely connect to the Directory Server backend.

Configuring Directory Server in SSL Mode

In order to configure the Directory Server in SSL mode, you must obtain and install a server certificate, configure the Directory Server to trust the CA’s certificate and enable SSL. Detailed instructions on how to complete these tasks are included in Chapter 11, “Managing Authentication and Encryption” in the Directory Server Administration Guide. This document can be found in the following location:

You can also download a PDF of the manual from the following location:

http://docs.sun.com/coll/DirectoryServer_04q2

If your Directory Server is already SSL-enabled, go to the next section for details on connecting Access Manager to Directory Server.

Connecting Access Manager to the SSL-enabled Directory Server

Once the Directory Server has been configured for SSL mode, you need to securely connect Access Manager to the Directory Server backend. To do so:

  1. In the Access Manager Console, go to the LDAP Authentication service in the Service Configuration module.
    1. Change the Directory Server port to the SSL port.
    2. Select the Enable SSL Access to LDAP Server attribute.
  2. Go to the Membership Authentication service in the Service Configuration module.
    1. Change the Directory Server port to the SSL port.
    2. Select the Enable SSL Access to LDAP Server attribute.
  3. Go to the Policy Configuration service located in Service Configuration.
    1. Change the Directory Server port to the SSL port.
    2. Select the Enable LDAP SSL attribute.
  4. Open the serverconfig.xml in a text editor. The file is in the following location:

    5. /etc/opt/SUNWam/config

    1. In the <Server> element, change the following values:

      2. port - enter the port number of the secure port to which Access Manager listens (636 is the default).

      type- change SIMPLE to SSL.

    2. Save and close serverconfig.xml.
  5. Open the AMConfig.properties file from the following default location:

    6. /etc/opt/SUNWam/config.

    Change the following properties:

    1. Directory Port = 636 (if using the default)
    2. ssl.enabed = true
    3. Save AMConfig.properties.
  6. Restart the server


Previous      Contents      Index      Next     

Part No: 817-7647-11.   Copyright 2005 Sun Microsystems, Inc. All rights reserved.