This third part of Deployment Example: SAML v2 Using Sun OpenSSO Enterprise 8.0 provides the instructions for installing and configuring OpenSSO Enterprise, Sun Java System Directory Server, applicable web containers and policy agents to function as the service provider. Best results will be obtained by executing the tasks in the exact sequence in which they are presented. This part contains the following chapters:
Chapter 7, Installing Sun Java System Directory Server and Creating Instances for User Data
Chapter 9, Configuring OpenSSO Enterprise Realms for User Authentication
Chapter 10, Configuring the Service Provider Protected Resource Host Machine
If deviating from the task sequence or details described, refer to the relevant product documentation for information or necessary requirements.
This chapter contains instructions for installing Sun Java™ System Directory Server and creating the instances in which Sun OpenSSO Enterprise user data will be stored. Additionally, the procedure for enabling multi-master replication between the two instances and the procedure for configuring the user data load balancer are included. This chapter contains the following sections:
7.1 Installing and Configuring Directory Server 1 and Directory Server 2
7.2 Enabling Multi-Master Replication of the User Data Instances
7.4 Enabling Secure Communication for the Directory Server User Data Instances
If you have an existing user data store, you can go directly to the instructions in Chapter 8, Deploying and Configuring OpenSSO Enterprise.
This section contains the instructions for installing Directory Server on two different host machines and creating the directory instances named sp-users in which the user data will be stored. Use the following list of procedures as a checklist for completing the task.
To Download the Directory Server Bits and Required Patches to the Directory Server Host Machines
To Create a Base Suffix for the User Data Instance on Directory Server 1
To Create a Base Suffix for the User Data Instance on Directory Server 2
Use this procedure to download the Directory Server Enterprise Edition (EE) 6.3 bits and the required system patches to both the Directory Server 1 host machine (ds1.sp-example.com) and the Directory Server 2 host machine (ds2.sp-example.com).
Access http://www.sun.com/software/products/directory_srvr_ee/get.jsp from a web browser and click Download Now.
Provide the following information in the Select product configuration section and click View Downloads.
Directory Server Enterprise Edition 6.x
6.3
Compress Archive (ZIP)
Choose the platform you are using.
The Selection Results page will be displayed with links to the download sites for the Directory Server bits and required patches.
The patch numbers generated for download on the Selection Results page are based on your input. Check the most recent Directory Server Enterprise Edition 6.1 Release Notes to determine if you need to install other patches based on your machine's architecture and operating system. In this deployment, the Release Notes indicate that based on the hardware and operating system being used, patch 118855, patch 127112, patch 119964, patch 125379, and patch 119255 are required.
Log into the ds1.sp-example.com host machine as a root user.
Run patchadd to see if the patches are already installed.
See the patchadd man page for more information.
# /usr/sbin/patchadd -p | grep 118855 |
No results are returned which indicates that the patch is not yet installed on the system.
# /usr/sbin/patchadd -p | grep 127112 |
No results are returned which indicates that the patch is not yet installed on the system.
# /usr/sbin/patchadd -p | grep 119964 |
No results are returned which indicates that the patch is not yet installed on the system.
# /usr/sbin/patchadd -p | grep 125379 |
No results are returned which indicates that the patch is not yet installed on the system.
# /usr/sbin/patchadd -p | grep 119255 |
No results are returned which indicates that the patch is not yet installed on the system.
If the necessary patches are already installed on your machine, proceed to step 7.
Make a directory for the patch downloads and change into it.
# mkdir /export/patches # cd /export/patches |
Download the patches.
You can click on the patch links from the Selection Results page or search for patches directly at http://sunsolve.sun.com. If searching directly, navigate to the PatchFinder page and enter the patch number. For each patch you are downloading, click the HTTP link beside the heading Download Signed Patch (xxx bytes).
Signed patches are downloaded as JAR files. Unsigned patches are downloaded as ZIP files. In this step, ZIP files are downloaded.
Make a directory for the Directory Server download and change into it.
# mkdir /export/DS63 # cd /export/DS63 |
Download the Base Full Install of Directory Server EE 6.3 — Zip Distribution, Multi-Language, (DS/DPS/DE/ISW/DSRK) bits.
No Directory Server Administration Console is installed with these bits. This deployment example uses the command line to configure the software.
Log out of the ds1.sp-example.com host machine.
Repeat this same procedure on the ds2.sp-example.com host machine.
If necessary, use this procedure to patch both the ds1.sp-example.com host machine and the ds2.sp-example.com host machine.
Log in to the ds1.sp-example.com host machine as a root user.
Change into the directory that contains the downloaded patch files.
# cd /export/patches |
Unzip the patch files.
# unzip 118855.zip # unzip 127112.zip # unzip 119964.zip # unzip 125379.zip # unzip 119255.zip |
Install the patches.
# /usr/sbin/patchadd /export/patches/118855 # /usr/sbin/patchadd /export/patches/127112 # /usr/sbin/patchadd /export/patches/119964 # /usr/sbin/patchadd /export/patches/125379 # /usr/sbin/patchadd /export/patches/119255 |
You can use the -M option to install all patches at once. See the patchadd man page for more information.
Reboot your machine, if requested.
After installation is complete, verify that each patch was added successfully.
# /usr/sbin/patchadd -p | grep 118855 |
A series of patch numbers are displayed, and the patch 118855 is present.
# /usr/sbin/patchadd -p | grep 127112 |
A series of patch numbers are displayed, and the patch 127112 is present.
# /usr/sbin/patchadd -p | grep 119964 |
A series of patch numbers are displayed, and the patch 119964 is present.
# /usr/sbin/patchadd -p | grep 125379 |
A series of patch numbers are displayed, and the patch 125379 is present.
# /usr/sbin/patchadd -p | grep 119255 |
A series of patch numbers are displayed, and the patch 119255 is present.
Log out of the ds1.sp-example.com host machine.
Repeat this same procedure on the ds2.sp-example.com host machine.
This procedures assumes To Download the Directory Server Bits and Required Patches to the Directory Server Host Machines and To Patch the Directory Server Host Machines have been completed.
Log in to the ds1.sp-example.com host machine as a root user.
(Optional) Resolve the following issues, if necessary.
The LD_LIBRARY_PATH environment variable should not be set to the default setting. Change the value to empty as in the following example:
# setenv LD_LIBRARY_PATH |
The JAVA_HOME environment variable should be set appropriately for your system architecture as in the following example:
# setenv JAVA_HOME /usr/jdk/jdk1.5.0_09 |
Unzip the Directory Server ZIP file.
# cd /export/DS63 # ls DSEE.6.3.Solaris10-X86_AMD64-full.tar.gz # gunzip DSEE.6.3.Solaris10-X86_AMD64-full.tar.gz |
Untar the resulting .tar file.
# tar xvf DSEE.6.1.Solaris10-X86_AMD64-full.tar |
The DSEE_ZIP_Distribution directory is the result of the decompression.
Change into DSEE_ZIP_Distribution and run dsee_deploy install to install Directory Server.
# cd DSEE_ZIP_Distribution # ./dsee_deploy install -i /var/opt/mps/serverroot |
The Licensing Agreement is displayed. At each Type return to continue prompt, press Return to continue.
When Do you accept the license terms? is displayed, enter yes to continue.
Once you accept the license terms, the Directory Server binaries will be installed in the /var/opt/mps/serverroot/ds6 directory.
Use this procedure to create a Directory Server instance named sp-users for storing user data. The instance uses port 1489 for LDAP and port 1736 for LDAPS.
This procedure assumes you have just completed To Install Directory Server 1 and are still logged into the ds1.sp-example.com host machine as a root user.
Change to the Directory Server bin directory.
# cd /var/opt/mps/serverroot/ds6/bin |
Run dsadm create to create a user data instance called sp-users.
# ./dsadm create -p 1489 -P 1736 /var/opt/mps/sp-users Choose the Directory Manager password: dsmanager Confirm the Directory Manager password: dsmanager use 'dsadm start /var/opt/mps/am-users' to start the instance |
Run dsadm start to start the instance.
# ./dsadm start /var/opt/mps/sp-users Directory Server instance '/var/opt/mps/sp-users' started: pid=11347 |
Run netstat to verify that the new instance is up and running.
# netstat -an | grep 1489 .1489 *.* 0 0 49152 0 LISTEN .1489 *.* 0 0 49152 0 LISTEN # netstat -an | grep 1736 .1736 *.* 0 0 49152 0 LISTEN .1736 *.* 0 0 49152 0 LISTEN |
Run ldapsearch to verify that you can read the root Directory Server entry of the new instance.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapsearch -h ds1.sp-example.com -p 1489 -b "" -s base "(objectclass=*)" version: 1 dn: objectClass: top ... supportedLDAPVersion: 3 vendorName: Sun Microsystems, Inc. vendorVersion: Sun-Java(tm)-System-Directory/6.3 ... |
Use this procedure to create the base suffix in which the user entries will be stored.
This procedure assumes you have just completed To Create a User Data Instance on Directory Server 1 and are still logged into the ds1.sp-example.com host machine as a root user.
Run dsconf create-suffix to create a base suffix.
# ./dsconf create-suffix -p 1489 -B dbExample -L /var/opt/mps/sp-users/db/exampleDS o=spusers.com |
Provide the appropriate information when prompted.
Certificate "CN=ds1, CN=1736, CN=directory Server, O=Sun Microsystems" presented by the server is not trusted. Type "Y" to accept, "y" to accept just once, "n" to refuse, "d" for more details: Y Enter "cn=Directory Manager" password: dsmanager |
When you type an uppercase Y, you are not asked for the certificate again in the next steps.
Run dsconf list-suffixes to verify that the base suffix was successfully created.
# ./dsconf list-suffixes -p 1489 Enter "cn=Directory Manager" password: dsmanager o=spusers.com |
If the base suffix was successfully created, o=spusers.com is returned. You can also see sp-users in a command line list of directory instances.
# cd /var/opt/mps # ls sp-users serverroot |
Log out of the ds1.sp-example.com host machine.
This procedures assumes To Download the Directory Server Bits and Required Patches to the Directory Server Host Machines and To Patch the Directory Server Host Machines have been completed.
Log in to the ds2.sp-example.com host machine as a root user.
(Optional) Resolve the following issues, if necessary.
The LD_LIBRARY_PATH environment variable should not be set to the default setting. Change the value to empty as in the following example:
# setenv LD_LIBRARY_PATH |
The JAVA_HOME environment variable should be set appropriately for your system architecture as in the following example:
# setenv JAVA_HOME /usr/jdk/jdk1.5.0_09 |
Unzip the Directory Server ZIP file.
# cd /export/DS63 # ls DSEE.6.3.Solaris-Sparc-full.tar.gz # gunzip DSEE.6.3.Solaris-Sparc-full.tar.gz |
Untar the resulting .tar file.
# tar xvf DSEE.6.3.Solaris-Sparc-full.tar |
The DSEE_ZIP_Distribution directory is the result of the decompression.
Change into DSEE_ZIP_Distribution and run dsee_deploy install to install Directory Server.
# cd DSEE_ZIP_Distribution # ./dsee_deploy install -i /var/opt/mps/serverroot |
The Licensing Agreement is displayed. At each Type return to continue prompt, press Return to continue.
When Do you accept the license terms? is displayed, enter yes to continue.
Once you accept the license terms, the Directory Server binaries will be installed in the /var/opt/mps/serverroot/ds6 directory.
Use this procedure to create a Directory Server instance named am-users for storing user data. The instance uses port 1489 for LDAP and port 1736 for LDAPS.
This procedure assumes you have just completed To Install Directory Server 2 and are still logged into the ds2.sp-example.com host machine as a root user.
Change to the Directory Server bin directory.
# cd /var/opt/mps/serverroot/ds6/bin |
Run dsadm create to create a user data instance called am-users.
# ./dsadm create -p 1489 -P 1736 /var/opt/mps/sp-users Choose the Directory Manager password: dsmanager Confirm the Directory Manager password: dsmanager use 'dsadm start /var/opt/mps/am-users' to start the instance |
Run dsadm start to start the instance.
# ./dsadm start /var/opt/mps/sp-users Directory Server instance '/var/opt/mps/sp-users' started: pid=7191 |
Run netstat to verify that the new instance is up and running.
# netstat -an | grep 1489 .1489 *.* 0 0 49152 0 LISTEN .1489 *.* 0 0 49152 0 LISTEN |
Run ldapsearch to verify that you can read the root Directory Server entry of the new instance.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapsearch -h ds2.sp-example.com -p 1489 -b "" -s base "(objectclass=*)" version: 1 dn: objectClass: top ... supportedLDAPVersion: 3 vendorName: Sun Microsystems, Inc. vendorVersion: Sun-Java(tm)-System-Directory/6.3 ... |
Use this procedure to create the base suffix in which the user entries will be stored.
This procedure assumes you have just completed To Create a User Data Instance on Directory Server 2 and are still logged into the ds2.sp-example.com host machine as a root user.
Run dsconf create-suffix to create a base suffix.
# ./dsconf create-suffix -p 1489 -B dbExample -L /var/opt/mps/am-users/db/exampleDS o=spusers.com |
Provide the appropriate information when prompted.
Certificate "CN=ds2, CN=1736, CN=directory Server, O=Sun Microsystems" presented by the server is not trusted. Type "Y" to accept, "y" to accept just once, "n" to refuse, "d" for more details: Y Enter "cn=Directory Manager" password: dsmanager |
When you type an uppercase Y, you are not asked for the certificate again in the next steps.
Run dsconf list-suffixes to verify that the base suffix was successfully created.
# ./dsconf list-suffixes -p 1489 Enter "cn=Directory Manager" password: dsmanager o=siroeusers.com |
If the base suffix was successfully created, o=spusers.com is returned. You can also see sp-users in a command line list of directory instances.
# cd /var/opt/mps # ls sp-users serverroot |
Log out of the ds2.sp-example.com host machine.
This section contains the instructions to enable multi-master replication (MMR) between two Directory Server instances, each configured as a master. This includes creating replication agreements between the masters and initializing the second directory master with the data and schema from the first directory master. The previously created sp-users user data instances will serve as the two master instances. Use the following list of procedures as a checklist for completing the task.
To Enable Multi-Master Replication for User Data Instance on Directory Server 1
To Enable Multi-Master Replication for User Data Instance on Directory Server 2
To Change the Default Replication Manager Password for Each User Data Instance
To Create Replication Agreements for Each User Data Instance
Log in to the ds1.sp-example.com host machine as a root user.
(Optional) Run dsconf list-suffixes to verify that the user data instance is not already enabled for replication.
# cd /var/opt/mps/serverroot/ds6/bin # ./dsconf list-suffixes -p 1489 -v Enter "cn=Directory Manager" password: dsmanager ... o=spusers.com 1 not-replicated N/A N/A 29 0 The "list-suffixes" operation succeeded on "ds1.sp-example.com:1489" |
The base suffix of the user data instance is not replicated.
Run dsconf enable-repl to enable replication of the user data instance.
# ./dsconf enable-repl -h ds1.sp-example.com -p 1489 -d 11 master o=spusers.com Enter "cn=Directory Manager" password: dsmanager Use "dsconf create-repl-agmt" to create replication agreements on "o=spusers.com". |
The -d option takes as input a randomly chosen identifier to represent the Directory Server 1 user data instance; in this case, 11 master indicates that the user data instance is a master and not a replica. The base suffix is specified as o=spusers.com.
Run dsconf list-suffixes again to verify that the instance is now enabled for replication.
# ./dsconf list-suffixes -p 1489 -v Enter "cn=Directory Manager" password: dsmanager ... o=siroeusers.com 1 master(11) N/A N/A 29 0 The "list-suffixes" operation succeeded on "ds1.sp-example.com:1489" |
The base suffix of the instance is master(11) indicating that the master was successfully enabled.
Log out of the ds1.sp-example.com host machine.
Log in to the ds2.sp-example.com host machine as a root user.
(Optional) Run dsconf list-suffixes to verify that the user data instance is not already enabled for replication.
# cd /var/opt/mps/serverroot/ds6/bin # ./dsconf list-suffixes -p 1489 -v Enter "cn=Directory Manager" password: dsmanager ... o=spusers.com 1 not-replicated N/A N/A 29 0 The "list-suffixes" operation succeeded on "ds2.sp-example.com:1489" |
The base suffix of the user data instance is not replicated.
Run dsconf enable-repl to enable replication of the user data instance.
# ./dsconf enable-repl -h ds2.sp-example.com -p 1489 -d 22 master o=spusers.com Enter "cn=Directory Manager" password: dsmanager Use "dsconf create-repl-agmt" to create replication agreements on "o=spusers.com". |
The -d option takes as input a randomly chosen identifier to represent the Directory Server 2 user data instance; in this case, 22 master indicates that the user data instance is a master and not a replica. The base suffix is specified as o=spusers.com.
Run dsconf list-suffixes again to verify that the instance is now enabled for replication.
# ./dsconf list-suffixes -p 1489 -v Enter "cn=Directory Manager" password: dsmanager ... o=spusers.com 1 master(22) N/A N/A 29 0 The "list-suffixes" operation succeeded on "ds2.sp-example.com:1489" |
The base suffix of the instance is master(22) indicating that the master was successfully enabled.
Log out of the ds2.sp-example.com host machine.
The replication manager is the user that data suppliers use to bind to the data consumer when sending replication updates. (In MMR the data consumer refers to whichever master happens to be the consumer for a particular operation.) It is recommended to change the default password created during the process of enabling replication.
Log in to the ds1.sp-example.com host machine as a root user.
Create a temporary file that contains the new replication manager password.
This file will be read once, and the password stored for future use.
# cd /var/opt/mps/serverroot/ds6/bin # echo replmanager > pwd.txt |
Verify that the file was successfully created.
# cat pwd.txt replmanager |
Run dsconf set-server-prop to set the replication manager password using pwd.txt as input.
# ./dsconf set-server-prop -h ds1.sp-example.com -p 1489 def-repl-manager-pwd-file:pwd.txt Enter "cn=Directory Manager" password: dsmanager |
Remove the pwd.txt file.
Log out of the ds1.sp-example.com host machine.
Log in to the ds2.sp-example.com host machine as a root user.
Create a temporary file that contains the new replication manager password.
This file will be read once, and the password stored for future use.
# cd /var/opt/mps/serverroot/ds6/bin # echo replmanager > pwd.txt |
Verify that the file was successfully created.
# cat pwd.txt replmanager |
Run dsconf set-server-prop to set the replication manager password using pwd.txt as input.
# ./dsconf set-server-prop -h ds2.sp-example.com -p 1489 def-repl-manager-pwd-file:pwd.txt Enter "cn=Directory Manager" password: dsmanager |
Remove the pwd.txt file.
Log out of the ds2.sp-example.com host machine.
A replication agreement is a set of parameters on a supplier that controls how updates are sent to a given consumer. In this deployment, the agreement simply makes the user data instances aware of each other.
Log in to the ds1.sp-example.com host machine as a root user.
Run dsconf create-repl-agmt to create the replication agreement.
# cd /var/opt/mps/serverroot/ds6/bin # ./dsconf create-repl-agmt -h ds1.sp-example.com -p 1489 o=spusers.com ds2.sp-example.com:1489 Enter "cn=Directory Manager" password: dsmanager Use "dsconf init-repl-dest o=spusers.com ds1.sp-example.com:1489" to start replication of "o=spusers.com" data. |
Run dsconf list-repl-agmts to verify that the replication agreement was successfully created.
# ./dsconf list-repl-agmts -p 1489 Enter "cn=Directory Manager" password: dsmanager o=spusers.com ds2.sp-example.com:1489 |
This response indicates that the Directory Server 1 base suffix will be replicated to Directory Server 2.
Log out of the ds1.sp-example.com host machine.
Log in to the ds2.sp-example.com host machine as a root user.
Run dsconf create-repl-agmt to create the replication agreement.
# cd /var/opt/mps/serverroot/ds6/bin # ./dsconf create-repl-agmt -h ds2.sp-example.com -p 1489 o=spusers.com ds1.sp-example.com:1489 Enter "cn=Directory Manager" password: dsmanager Use "dsconf init-repl-dest o=spusers.com ds1.sp-example.com:1489" to start replication of "o=spusers.com" data. |
Run dsconf list-repl-agmts to verify that the replication agreement was successfully created.
# ./dsconf list-repl-agmts -p 1489 Enter "cn=Directory Manager" password: dsmanager o=spusers.com ds1.sp-example.com:1489 |
This response indicates that the Directory Server 2 base suffix will be replicated to Directory Server 1.
Log out of the ds2.sp-example.com host machine.
Use this procedure to initialize the user data instance on Directory Server 1. The previously created agreements will replicate the data to Directory Server 2.
Initialization is not required on both instances when configuring for MMR.
Log in to the ds1.sp-example.com host machine as a root user.
Run dsconf show-repl-agmt-status to verify that the replication agreements have not yet been initialized.
# cd /var/opt/mps/serverroot/ds6/bin # ./dsconf show-repl-agmt-status -h ds1.sp-example.com -p 1489 o=spusers.com ds2.sp-example.com:1489 Enter "cn=Directory Manager" password: dsmanager Configuration Status : OK Authentication Status : OK Initialization Status : NOT OK Status: : Dest. Not Initialized |
Run dsconf init-repl-dest to initialize the replication agreements.
# ./dsconf init-repl-dest -h ds1.sp-example.com -p 1489 o=spusers.com ds2.sp-example.com:1489 Enter "cn=Directory Manager" password: dsmanager Started initialization of "ds2.sp-example.com:1489"; Sep 13, 2008 9:58:08 AM Sent 2 entries. Completed initialization of "ds2.sp-example.com:1489"; Sep 13, 2008 9:58:12 AM |
Run dsconf show-repl-agmt-status again to verify that the replication agreements are now initialized.
# ./dsconf show-repl-agmt-status -h ds1.sp-example.com -p 1489 o=spusers.com ds2.sp-example.com:1489 Enter "cn=Directory Manager" password: dsmanager Configuration Status : OK Authentication Status : OK Initialization Status : OK Status: : Enabled Last Update Date : Sep 13, 2008 9:58:17 AM |
This procedure assumes you have just completed To Initialize the Replication Agreements and are still logged into the ds2.sp-example.com host machine as a root user.
Prepare an LDIF file with the following contents and save it in the /tmp directory as people.ldif.
dn: ou=People,o=spusers.com objectclass: top objectclass: organizationalUnit ou: People description: Container for user entries
Run ldapmodify on the ds1.sp-example.com host machine using people.ldif as input.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapmodify -a -h ds1.sp-example.com -p 1489 -f /tmp/people.ldif -D cn=Directory Manager,cn=Administrators,cn=config -w dsmanager adding new entry ou=People,o=spusers.com |
After the entry is created, log in to the ds2.sp-example.com host machine as a root user.
Run ldapsearch on Directory Server 2 to verify that ou=People was successfully replicated.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapsearch -b "o=spusers.com" -p 1489 -D "cn=Directory Manager" -w dsmanager "objectclass=organizationalUnit" version: 1 dn: ou=People,o=spusers.com objectClass: top objectClass: organizationalUnit ou: People description Container for user entries |
Now run ldapdelete on Directory Server 2 to delete ou=People.
# ./ldapdelete -h ds2.sp-example.com -p 1489 -D "cn=Directory Manager" -w dsmanager "ou=People,o=spusers.com" |
Now, as a root user on Directory Server 1, run ldapsearch to verify that the deletion was replicated.
# ./ldapsearch -b "o=spusers.com" -p 1489 -D "cn=Directory Manager" -w dsmanager "objectclass=organizationalUnit" |
The search will return no results as the delete was successfully replicated.
Log out of both Directory Server host machines.
This deployment will be used to test SAML v2 communications. Towards this end, modify the LDAP schema used by the Directory Server user data instances on the service provider side to recognize and store SAML v2 attributes.
Log in to the ds2.sp-example.com host machine as a root user.
Create an LDIF file with the following information and save it as /tmp/saml.ldif.
This file includes SAML v2 LDAP attributes.
dn: CN=schema changetype:modify add:attributeTypes attributeTypes: ( 1.3.6.1.4.1.42.2.27.9.1.500 NAME 'sun-fm-saml2-nameid-infokey' DESC 'SAML 2.0 Name Identifier Information Key' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'Sun Java System Access Management' ) attributeTypes: ( 1.3.6.1.4.1.42.2.27.9.1.501 NAME 'sun-fm-saml2-nameid-info' DESC 'SAML 2.0 Name Identifier Information' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'Sun Java System Access Management' ) - add:objectClasses objectClasses: ( 1.3.6.1.4.1.42.2.27.9.2.200 NAME 'sunFMSAML2NameIdentifier' DESC 'SAML 2.0 name identifier objectclass' SUP top AUXILIARY MAY ( sun-fm-saml2-nameid-infokey $ sun-fm-saml2-nameid-info ) X-ORIGIN 'Sun Java System Access Management' ) |
Run ldapmodify on the ds1.sp-example.com host machine using /tmp/saml.ldif as input.
# cd /var/opt/mps/serverroot/dsrk6/bin # ldapmodify -a -h ds2.sp-example.com -p 1489 -D "cn=Directory Manager" -w dsmanager -f /tmp/saml.ldif modifying entry CN=schema |
Log out of the ds1.idp-example.com host machine.
By default, when an instance of Directory Server is created (in this case, sp-users), its SSL port is secured with a self-signed certificate named defaultCert. A self-signed certificate contains a public and private key; the public key is signed by the private key. The sp-users instances, though, need to use a server certificate signed by a certificate authority (CA) to allow for secure communication between the instances and the soon-to-be-installed user data load balancer. This entails installing the server certificate signed by the CA and the root certificate confirming the signature of the CA on both Directory Server host machines. Use the following list of procedures as a checklist for completing this task.
To Install a Root Certificate and a Server Certificate on Directory Server 1
To Install a Root Certificate and a Server Certificate on Directory Server 2
You should already have a root certificate from the CA of your choice. Send server certificate requests to the same CA. For more information, see 3.3 Obtaining Secure Socket Layer Certificates.
Log in to the ds1.sp-example.com host machine as a root user.
Generate a request for a server certificate signed by a CA.
# cd /var/opt/mps/serverroot/ds6/bin # ./dsadm request-cert -S "CN=ds1.sp-example.com, OU=OpenSSO Enterprise, O=Sun Microsystems, L=Santa Clara ST=California, C=US" -F ascii -o ds-1.csr /var/opt/mps/sp-users |
ds-1.csr is the certificate request.
Send ds-1.csr to the CA of your choice.
The CA issues and returns a certified server certificate named ds-1.cer.
Add ds-1.cer, the CA-signed server certificate, to the certificate store.
# ./dsadm add-cert /var/opt/mps/sp-users server-cert ds-1.cer |
Add ca.cer, the CA root certificate, to the certificate store.
# ./dsadm add-cert --ca /var/opt/mps/sp-users opensslCA ca.cer |
(Optional) Verify that the CA root certificate was successfully added.
# ./dsadm list-certs -C /var/opt/mps/sp-users | grep opensslCA opensslCA 2008/02/06 00:00 2017/02/06 00:00 n CN=Certificate Manager,OU=opensso,O=Identity,C=US Same as issuer |
Configure the Directory Server instance to use the imported certificates.
# ./dsconf set-server-prop -h ds1.sp-example.com -p 1489 ssl-rsa-cert-name:server-cert Enter "cn=Directory Manager" password: dsmanager Before setting SSL configuration, export Directory Server data. Do you want to continue [y/n] ? y Directory Server must be restarted for changes to take effect. |
Restart the Directory Server instance.
Directory Server needs to be restarted to use the new certificates.
# ./dsadm stop /var/opt/mps/sp-users Directory Server instance '/var/opt/mps/sp-users' stopped # ./dsadm start /var/opt/mps/sp-users Directory Server instance '/var/opt/mps/sp-users' started: pid=11591 |
Run ldapsearch on Directory Server 1 to verify that the directory entries can be accessed through the secure port.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapsearch -h ds1.sp-example.com -p 1736 -Z -P /var/opt/mps/sp-users/alias/slapd-cert8.db -b "" -s base "(objectclass=*)" version: 1 dn: objectClass:top namingContexts: o=spusers.com supportedExtension: 2.16.840.1.113730.3.5.7 : supportedSSLCiphers: SSL-CK_RC4_128_EXPORT40_WITH_MD5 supportedSSLCiphers: SSL-CK_RC2_128_CBC_EXPORT40_WITH_MD5 |
This confirms that the Directory Server instance can be accessed through the secure port.
Log out of the ds1.sp-example.com host machine.
You should already have a root certificate from the CA of your choice. Send any server certificate requests to the same CA. For more information, see 3.3 Obtaining Secure Socket Layer Certificates.
Log in to the ds2.sp-example.com host machine as a root user.
Generate a request for a server certificate signed by a CA.
# cd /var/opt/mps/serverroot/ds6/bin # ./dsadm request-cert -S "CN=ds2.sp-example.com, OU=OpenSSO Enterprise, O=Sun Microsystems, L=Santa Clara ST=California, C=US" -F ascii -o ds-2.csr /var/opt/mps/sp-users |
ds-2.csr is the certificate request.
Send ds-2.csr to the CA of your choice.
The CA issues and returns a certified server certificate named ds-2.cer.
Add ds-2.cer, the CA-signed server certificate, to the certificate store.
# ./dsadm add-cert /var/opt/mps/sp-users server-cert ds-2.cer |
Add ca.cer, the CA root certificate, to the certificate store.
# ./dsadm add-cert --ca /var/opt/mps/sp-users opensslCA ca.cer |
(Optional) Verify that the CA root certificate was successfully added.
# ./dsadm list-certs -C /var/opt/mps/sp-users | grep opensslCA opensslCA 2008/02/06 00:00 2017/02/06 00:00 n CN=Certificate Manager,OU=opensso,O=Identity,C=us Same as issuer |
Configure the Directory Server instance to use the imported certificates.
# ./dsconf set-server-prop -h ds2.sp-example.com -p 1489 ssl-rsa-cert-name:server-cert Enter "cn=Directory Manager" password: dsmanager Before setting SSL configuration, export Directory Server data. Do you want to continue [y/n] ? y Directory Server must be restarted for changes to take effect. |
Restart the Directory Server instance.
Directory Server needs to be restarted to use the new certificates.
# ./dsadm stop /var/opt/mps/sp-users Directory Server instance '/var/opt/mps/sp-users' stopped # ./dsadm start /var/opt/mps/sp-users Directory Server instance '/var/opt/mps/sp-users' started: pid=7311 |
Run ldapsearch on Directory Server 2 to verify that the directory entries can be accessed through the secure port.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapsearch -h ds2.sp-example.com -p 1736 -Z -P /var/opt/mps/sp-users/alias/slapd-cert8.db -b "" -s base "(objectclass=*)" version: 1 dn: objectClass:top namingContexts: o=spusers.com supportedExtension: 2.16.840.1.113730.3.5.7 : supportedSSLCiphers: SSL-CK_RC4_128_EXPORT40_WITH_MD5 supportedSSLCiphers: SSL-CK_RC2_128_CBC_EXPORT40_WITH_MD5 |
This confirms that the Directory Server instance can be accessed through the secure port.
Log out of the ds2.sp-example.com host machine.
Load Balancer 1 (lb1.sp-example.com) is configured in front of the Directory Server user data instances on the service provider side. This section assumes that you have already installed the load balancer. Before beginning, note the following:
The load balancer hardware and software used in the lab facility for this deployment is BIG-IP® manufactured by F5 Networks. If you are using different load balancer software, see the documentation that comes with that product for detailed settings information.
Contact your network administrator to obtain an available virtual IP address for the load balancer you want to configure.
Know the IP address of the load balancer hardware, the URL for the load balancer login page, and a username and password for logging in to the load balancer application.
Get the IP addresses for Directory Server 1 and Directory Server 2 by running the following command on each host machine:
# ifconfig -a |
Use the following list of procedures as a checklist for completing the task.
Install the CA root certificate on the user data load balancer to ensure that a link between the load balancer can be maintained with the CA. Use the same root certificate that you imported in 7.4 Enabling Secure Communication for the Directory Server User Data Instances. For more information, see 3.3 Obtaining Secure Socket Layer Certificates.
Access https://is-f5.siroe.com, the BIG-IP load balancer login page, in a web browser.
Log in to the load balancer as administrator.
Click Proxies.
Click the Cert-Admin tab.
Click Import.
In the Import Type field, choose Certificate and click Continue.
Click Browse in the Certificate File field on the Install SSL Certificate page.
Choose Browser in the Choose File dialog box.
Navigate to ca.cer and click Open.
Enter opensslCA in the Certificate Identifier field.
Click Install Certificate.
The Certificate opensslCA page is displayed.
Click Return to Certificate Administration on the Certificate opensslCA page.
opensslCA, the root certificate, is now included in the Certificate ID list.
This procedure assumes that you have just completed To Import the Root Certificate to the User Data Load Balancer and are still logged into the load balancer console.
Click Configure your BIG-IP (R) using the Configuration Utility.
Create a Pool.
A pool contains all the backend server instances.
In the left pane, click Pools.
On the Pools tab, click Add.
In the Add Pool dialog, provide the following information:
DirectoryServerSP-UserData-Pool
Round Robin
Add the IP address and port number of both Directory Server host machines.
Use port number 1489.
Click Done.
Add a Virtual Server.
The virtual server presents an address to the outside world and, when users attempt to connect, it would forward the connection to the most appropriate real server.
If you encounter JavaScriptTM errors or otherwise cannot proceed to create a virtual server, try using Internet Explorer.
In the left frame, click Virtual Servers.
Click Add on the Virtual Servers tab.
In the Add a Virtual Server dialog box, provide the following information:
Enter the IP address for lb1.sp-example.com
489
Continue to click Next until you reach the Pool Selection dialog box.
Assign DirectoryServerSP-UserData-Pool to the virtual server in the Pool Selection dialog box.
Click Done.
Add Monitors
Monitors are required for the load balancer to detect the backend server failures.
In the left frame, click Monitors.
Click the Basic Associations tab.
Add an LDAP monitor for the Directory Server 1 node.
In the Node column, locate the IP address and port number previously entered for Directory Server 1 and select the Add checkbox.
Add an LDAP monitor for the Directory Server 2 node.
In the Node column, locate the IP address and port number previously entered for Directory Server 2 and select the Add checkbox.
At the top of the Node column, in the drop-down list, choose ldap-tcp.
Click Apply.
Configure the load balancer for simple persistence.
With simple persistence, all requests sent within a specified interval are processed by the same Directory Server instance, ensuring complete replication of entries. For example, when a request requires information to be written to Directory Server 1, that information must also be replicated to Directory Server 2. As the replication takes time to complete, if a related request is directed by the load balancer to Directory Server 2 during the replication process itself, the request may fail as the entry might only be partially created. When properly configured, simple persistence ensures that both requests are routed to Directory Server 1 and processed in consecutive order; the first request is finished before the second request begins processing. Simple persistence ensures that within the specified interval, no errors or delays occur due to replication time or redirects when retrieving data. Simple persistence tracks connections based only on the client IP address.
Verify the Directory Server load balancer configuration using the following sub-procedure.
Log in as a root user on each Directory Server host machine.
On each host machine, use the tail command to monitor the Directory Server access log.
# cd /var/opt/mps/sp-users/logs # tail -f access |
You should see connections to the load balancer IP address opening and closing. For example:
[12/July/2008:13:10:20-0700] conn=69755 op=-1 msgId=-1 - closed [12/July/2008:13:10:25-0700] conn=69756 op=-1 msgId=-1 - fd=27 slot=27 LDAP connection from IP_address to IP_address [12/July/2008:13:10:25-0700] conn=69756 op=0 msgId=0 - RESULT err=80 tag=120 nentries=0 etime=0 [12/July/2008:13:10:25-0700] conn=69756 op=-1 msgId=-1 - closing from IP_address
Execute the following LDAP search against the Directory Server load balancer from Directory Server 1.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapsearch -h lb1.sp-example.com -p 489 -Z -P /var/opt/mps/sp-users/alias/slapd-cert8.db -b "o=spusers.com" -D "cn=directory manager" -w dsmanager "(objectclass=*)" version: 1 dn: o=spusers.com objectClass: top objectClass: organization o: spusers.com |
Make sure the returned entries display in the access log on only one Directory Server host machine.
Run dsadm stop to stop Directory Server 1.
# cd /var/opt/mps/serverroot/ds6/bin # ./dsadm stop /var/opt/mps/sp-users |
Perform the (same) LDAP search against the Directory Server load balancer from Directory Server 2.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapsearch -h lb1.sp-example.com -p 489 -Z -P /var/opt/mps/sp-users/alias/slapd-cert8.db -b "o=spusers.com" -D "cn=directory manager" -w dsmanager "(objectclass=*)" version: 1 dn: o=spusers.com objectClass: top objectClass: organization o: spusers.com |
Make sure the returned entries display in the access log on only Directory Server 2.
You may encounter the following error message:
ldap_simple_bind: Cant' connect to the LDAP server — Connection refused
This means that the load balancer may not fully detect that Directory Server 1 is stopped. In this case, you may have started the search too soon based on the polling interval setting. For example, if the polling interval is set to 10 seconds, you should wait ten seconds to start the search. You can reset the timeout properties to a lower value using the load balancer console.
Click the Monitors tab.
Click the ldap-tcp monitor name.
In the Interval field, set the value to 5.
This tells the load balancer to poll the server every 5 seconds.
In the Timeout field, set the value to 16.
Click Apply and repeat the LDAP search.
See your load balancer documentation for more information on the timeout property.
Start Directory Server 1.
# ./dsadm start /var/opt/mps/sp-users |
Stop Directory Server 2.
# cd /var/opt/mps/serverroot/ds6/bin # ./dsadm stop /var/opt/mps/sp-users |
Perform the (same) LDAP search against the Directory Server load balancer from Directory Server 1 to confirm that the request is forwarded to the running Directory Server 1.
# cd /var/opt/mps/serverroot/dsrk6/bin ./ldapsearch -h lb1.sp-example.com -p 489 -Z -P /var/opt/mps/am-users/alias/slapd-cert8.db -b "o=spusers.com" -D "cn=directory manager" -w dsmanager "(objectclass=*)" version: 1 dn: o=spusers.com objectClass: top objectClass: organization o: spusers.com |
Make sure the returned entries display in the access log on only Directory Server 1.
Start Directory Server 2.
# ./dsadm start /var/opt/mps/sp-users |
Log out of both Directory Server host machines and the load balancer console.
Create a user entry in the replicated Directory Server user data instances for spuser.
If you are using an existing user data store, create the appropriate users in it and move on to Chapter 9, Configuring OpenSSO Enterprise Realms for User Authentication.
Create an LDIF file for the test user and import the file into ds1.sp-example.com. The test user data will then be replicated to ds2.sp-example.com.
Log in to the ds1.sp-example.com host machine as a root user.
Create an LDIF file with the following entries.
dn: ou=users,o=spusers.com objectclass: top objectclass: organizationalUnit ou: users description: Container for user entries dn: ou=Groups,o=spusers.com objectClass: top objectClass: organizationalUnit ou: Groups description: Container for group entries dn: uid=spuser,ou=users,o=spusers.com uid: spuser givenName: sp objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetadmin objectClass: inetorgperson objectClass: inetUser sn: user cn: sp user userPassword: spuser inetUserStatus: Active
Save the file as sp-users.ldif in the /tmp directory.
Import the LDIF file into Directory Server 1 using ldapmodify.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapmodify -h ds1.sp-example.com -p 1489 -D "cn=Directory Manager" -w dsmanager -a -f /tmp/sp-users.ldif adding new entry ou=users,o=spusers.com adding new entry ou=Groups,o=spusers.com adding new entry uid=spuser,ou=users,o=spusers.com |
Verify that the new users were imported using ldapsearch.
# ./ldapsearch -h ds1.sp-example.com -b "o=spusers.com" -p 1489 -D "cn=Directory Manager" -w dsmanager "uid=spuser" version: 1 dn: uid=spuser,ou=users,o=spusers.com uid: spuser givenName: sp objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetadmin objectClass: inetorgperson objectClass: inetUser sn: user cn: sp user userPassword: {SSHA}H5LpB+QLZMoL9SiXzY/DokHKXRclELVy7w25AA== inetUserStatus: Active |
Log out of the ds1.sp-example.com host machine.
(Optional) Verify that the entries were replicated to Directory Server 2 by logging in as a root user to the ds2.idp-example.com host machine and using ldapsearch.
# cd /var/opt/mps/serverroot/dsrk6/bin # ./ldapsearch -h ds2.sp-example.com -b "o=spusers.com" -p 1489 -D "cn=Directory Manager" -w dsmanager "" version: 1 dn: o=spusers.com objectClass: top objectClass: domain dc: company dn: ou=users,o=spusers.com objectClass: top objectClass: organizationalUnit ou: users description: Container for user entries dn: ou=Groups,o=spusers.com objectClass: top objectClass: organizationalUnit ou: Groups description: Container for group entries dn: uid=spuser,ou=users,o=spusers.com uid: spuser givenName: sp objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetadmin objectClass: inetorgperson objectClass: inetUser sn: user cn: sp user userPassword: {SSHA}H5LpB+QLZMoL9SiXzY/DokHKXRclELVy7w25AA== inetUserStatus: Active |
Log out of the ds2.sp-example.com host machine.
This chapter includes instructions on how to deploy and configure two instances of Sun OpenSSO Enterprise 8.0 on the service provider side. It begins with the installation of Sun Java™ System Application Server onto each host machine, followed by the deployment and configuration of the OpenSSO Enterprise WAR. This chapter contains the following sections:
In this section, we create a non-root user with the roleadd command in the Solaris Operating Environment on each OpenSSO Enterprise host machine and install Sun Java System Application Server 9.1 Update 1 using the non-root user. Use the following list of procedures as a checklist for completing the task.
To Create a Non-Root User on the OpenSSO Enterprise 1 Host Machine
To Install Application Server on the OpenSSO Enterprise 1 Host Machine
To Create a Non-Root User on the OpenSSO Enterprise 2 Host Machine
To Install Application Server on the OpenSSO Enterprise 2 Host Machine
We use roleadd rather than useradd for security reasons; roleadd disables the ability of the user to log in.
On our lab machines, the required Application Server patch is 117461–08. Results for your machine might be different. Read the latest documentation for your web container to determine if you need to install patches and, if so, what they might be. You can search for patches directly at http://sunsolve.sun.com. Navigate to the PatchFinder page, enter the patch number, click Find Patch, and download the appropriate patch for the OpenSSO Enterprise 1 host machine (osso1.sp-example.com) and the OpenSSO Enterprise 2 host machine (osso2.sp-example.com).
Log in to the osso1.sp-example.com host machine as a root user.
Run patchadd to see if the patch is already installed.
# patchadd -p | grep 117461-08 |
A series of patch numbers are displayed, and patch 117461–08 is present so there is no need to install any patches at this time.
Log out of the osso1.sp-example.com host machine.
Log in to the osso2.sp-example.com host machine as a root user.
Run patchadd to see if the patch is already installed.
# patchadd -p | grep 117461-08 |
A series of patch numbers are displayed, and patch 117461–08 is present so there is no need to install any patches at this time.
Log out of the osso1.sp-example.com host machine.
Log in to the osso1.sp-example.com host machine as a root user.
Create a new user with roleadd.
# roleadd -s /sbin/sh -m -g staff -d /export/osso80adm osso80adm |
(Optional) Verify that the user was created.
# cat /etc/passwd root:x:0:0:Super-User:/:/sbin/sh daemon:x:1:1::/: ... nobody4:x:65534:65534:SunOS 4.x NFS Anonymous Access User:/: osso80adm:x:223830:10::/export/osso80adm:/sbin/sh |
(Optional) Verify that the user's directory was created.
# cd /export/osso80adm # ls local.cshrc local.profile local.login |
Create a password for the non-root user.
# passwd osso80adm New Password: nonroot1pwd Re-ener new Pasword: nonroot1pwd passwd: password successfully changed for osso80adm |
If you do not perform this step, you will not be able to switch user (su) when logged in as the non-root user.
Install Application Server and the appropriate CA root and CA-signed server certificates.
This procedure assumes you have just completed To Create a Non-Root User on the OpenSSO Enterprise 1 Host Machine and are still logged into the osso1.sp-example.com host machine as a root user.
Create a directory into which the Application Server bits can be downloaded and change into it.
# mkdir /export/AS91 # cd /export/AS91 |
Download the Sun Java System Application Server 9.1 Update 2 binary from the Sun Microsystems Product Download page to the /export/AS91 directory.
Grant the downloaded binary execute permission using the chmod command.
# chmod +x sjsas-9_1_02-solaris-sparc-ml.bin |
Install the software.
# ./sjsas-9_1_02-solaris-sparc-ml.bin -console |
When prompted, provide the following information.
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Press Enter to display the Software License Agreement. |
|
|
Type yes and press Enter. |
|
|
Enter /opt/SUNWappserver91 |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the default value. |
|
|
Enter domain1pwd and then re-enter domain1pwd. |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the three default values. |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the default value and begin the installation process. |
|
|
When installation is complete, an Installation Successful message is displayed: |
|
|
Press Enter to exit the installation program. |
Create a second Application Server domain for the non-root user.
The default domain created during the installation process is owned by root. We create a new domain for osso80adm, the non-root user, into which we will deploy OpenSSO Enterprise.
# cd /opt/SUNWappserver91/bin # su osso80adm # ./asadmin create-domain --domaindir /export/osso80adm/domains --adminport 8989 --user domain2adm --instanceport 1080 --domainproperties http.ssl.port=1081 ossodomain Please enter the admin password> domain2pwd Please enter the admin password again> domain2pwd Please enter the master password [Enter to accept the default]:> domain2master Please enter the master password again [Enter to accept the default]:> domain2master Using port 8989 for Admin. Using port 1080 for HTTP Instance. Using default port 7676 for JMS. Using default port 3700 for IIOP. Using port 1081 for HTTP_SSL. Using default port 3820 for IIOP_SSL. Using default port 3920 for IIOP_MUTUALAUTH. Using default port 8686 for JMX_ADMIN. Domain being created with profile:developer, as specified by variable AS_ADMIN_PROFILE in configuration file. Security Store uses: JKS 2008-09-14 18:21:15.907 GMT Thread[main,5,main] java.io.FileNotFoundException: derby.log (Permission denied) ------------------------------------------------- 2008-09-14 18:21:16.216 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.1 - (538595): instance c013800d-0118-e205-d50b-00000c0c0770 on database directory /export/osso80adm/domains/ossodomain/lib/databases/ejbtimer Database Class Loader started - derby.database.classpath='' Domain ossodomain created. |
Creating a non-root domain displays a FileNotFoundException. Please see Appendix G, Known Issues and Limitations.
Verify that the non-root user domain was created with the correct permissions using the following sub-procedure.
Change to the ossodomain directory.
# cd /export/osso80adm/domains/ossodomain |
List the contents of the directory.
# ls -la total 30 drwxr-xr-x 15 osso80adm staff 512 Sep 14 16:43 . drwxr-xr-x 3 osso80adm staff 512 Sep 14 16:43 .. drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 addons drwxr-xr-x 6 osso80adm staff 512 Sep 14 16:43 applications drwxr-xr-x 3 osso80adm staff 512 Sep 14 16:43 autodeploy drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 bin drwx------ 3 osso80adm staff 1024 Sep 14 16:43 config drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 docroot drwxr-xr-x 6 osso80adm staff 512 Sep 14 16:43 generated drwxr-xr-x 3 osso80adm staff 512 Sep 14 16:43 imq drwxr-xr-x 5 osso80adm staff 512 Sep 14 16:43 java-web-start drwxr-xr-x 8 osso80adm staff 512 Sep 14 16:43 jbi drwxr-xr-x 6 osso80adm staff 512 Sep 14 16:43 lib drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 logs drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 session-store |
The files and directories are owned by osso80adm.
Start ossodomain, the non-root user domain, using the following sub-procedure.
Verify that ossodomain has started with the following sub-procedure.
Access http://osso1.sp-example.com:8989/login.jsf from a web browser.
Log in to the Application Server console as the ossodomain administrator.
domain2adm
domain2pwd
When the Application Server administration console is displayed, it is verification that the non-root user was able to start the domain server.
Exit the console and close the browser.
Create a request for a CA-signed server certificate to secure communications between the soon-to-be-configured OpenSSO Enterprise load balancer and ossodomain using the following sub-procedure.
Generate a private/public key pair and reference it with the alias, opensso-sp-1.
opensso-sp-1 will be used in a later step to retrieve the public key which is contained in a self-signed certificate.
# cd /export/osso80adm/domains/ossodomain/config # keytool -genkey -noprompt -keyalg rsa -keypass domain2master -alias opensso-sp-1 -keystore keystore.jks -dname "CN=osso1.sp-example.com, OU=OpenSSO, O=Sun Microsystems, L=Santa Clara, ST=California, C=US" -storepass domain2master |
Verify that the key pair was successfully created and stored in the certificate store.
# keytool -list -v -keystore keystore.jks -storepass domain2master Keystore type: jks Keystore provider: SUN Your keystore contains two entries. ... Alias name: opensso-sp-1 Creation date: Sep 14, 2008 Entry type: keyEntry Certificate chain length: 1 Certificate[1]: Owner: CN=osso1.sp-example.com, OU=OpenSSO, O=Sun Microsystems, L=Santa Clara, ST=California, C=US Issuer: CN=osso-osso1.sp-example.com, OU=OpenSSO, O=Sun Microsystems, L=Santa Clara, ST=California, C=US Serial number: 48cdb299 Valid from: Sun Sep 14 15:02:47 PDT 2008 until: Sat Dec 13 15:02:47 PDT 2008 Certificate fingerprints: MD5: 14:0F:88:BC:C8:6F:2C:8B:F0:A2:C2:F1:AF:FC:93:F1: SHA1: 9D:22:05:14:51:21:33:CB:06:36:25:FE:0A:B6:DF:45:EE:B1:19:86: |
The output of this command may list more than one certificate based on the entries in the keystore.
Generate a CA-signed server certificate request.
# keytool -certreq -alias opensso-sp-1 -keypass domain2master -keystore keystore.jks -storepass domain2master file opensso-sp-1.csr |
opensso-sp-1.csr is the server certificate request.
(Optional) Verify that opensso-sp-1.csr was created.
# ls -la opensso-sp-1.csr -rw-r--r-- 1 osso80adm staff 715 Sep 14 15:04 opensso-sp-1.csr |
Send osso-sp-1.csr to the CA of your choice.
The CA issues and returns a certified certificate named opensso-sp-1.cer.
Import ca.cer, the CA root certificate.
The root certificate must be imported into two keystores (keystore.jks and cacerts.jks) with Application Server. Use the same root certificate that you imported in 7.4 Enabling Secure Communication for the Directory Server User Data Instances. For more information, see 3.3 Obtaining Secure Socket Layer Certificates.
# keytool -import -trustcacerts -alias OpenSSLTestCA -file ca.cer -keystore keystore.jks -storepass domain2master Owner: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=am, O=sun, L=santa clara, ST=california, C=us Issuer: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=am, O=sun, L=santa clara, ST=california, C=us Serial number: f59cd13935f5f498 Valid from: Thu Sep 20 11:41:51 PDT 2007 until: Thu Jun 17 11:41:51 PDT 2010 Certificate fingerprints: MD5: 78:7D:F0:04:8A:5B:5D:63:F5:EC:5B:21:14:9C:8A:B9 SHA1: A4:27:8A:B0:45:7A:EE:16:31:DC:E5:32:46:61:9E:B8:A3:20:8C:BA Trust this certificate? [no]: Yes Certificate was added to keystore |
# keytool -import -trustcacerts -alias OpenSSLTestCA -file ca.cer -keystore cacerts.jks -storepass ossomaster Owner: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=am, O=sun, L=santa clara, ST=california, C=us Issuer: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=am, O=sun, L=santa clara, ST=california, C=us Serial number: f59cd13935f5f498 Valid from: Thu Sep 20 11:41:51 PDT 2007 until: Thu Jun 17 11:41:51 PDT 2010 Certificate fingerprints: MD5: 78:7D:F0:04:8A:5B:5D:63:F5:EC:5B:21:14:9C:8A:B9 SHA1: A4:27:8A:B0:45:7A:EE:16:31:DC:E5:32:46:61:9E:B8:A3:20:8C:BA Trust this certificate? [no]: Yes Certificate was added to keystore |
Replace the self-signed public key certificate (associated with the s1as alias) with the CA-signed server certificate.
# keytool -import -file opensso-sp-1.cer -alias opensso-sp-1 -keystore keystore.jks -storepass domain2master Certificate reply was installed in keystore |
(Optional) Verify that the self-signed public key certificate has been overwritten by the server certificate received from the CA.
# keytool -list -v -keystore keystore.jks -storepass domain2master The certificate indicated by the alias "osso-sp-1" is signed by CA. |
Change the certificate alias from the default s1as to the new opensso-sp-1 in the domain.xml file for the ossodomain domain.
The Application Server configuration file is domain.xml.
<http-listener acceptor-threads="1" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-2" port="1081" security-enabled="true" server-name="" xpowered-by="true"> <ssl cert-nickname="opensso-sp-1" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
Backup domain.xml before modifying it.
Modify the JVM options in your web container's configuration file using the following sub-procedure.
OpenSSO Enterprise is deployed with an embedded configuration data store (if desired). In order for the configuration data store to be created successfully, the following JVM options should be modified in the web container's configuration file. We will be modifying domain.xml again for this example.
Backup domain.xml before modifying it.
Change to the config directory.
# cd /export/osso80adm/domains/ossodomain/config |
Open domain.xml in a text editor and make the following changes:
Replace <jvm-options>-client</jvm-options> with <jvm-options>-server</jvm-options>.
Replace <jvm-options>-Xmx512m</jvm-options> with <jvm-options>-Xmx1024m</jvm-options>.
Save the file and close it.
Restart the ossodomain domain.
# cd /export/osso80adm/domains/ossodomain/bin # ./stopserv Server was successfully stopped. ./startserv admin username:domain2adm admin password:domain2pwd master password:domain2master Redirecting output to /export/osso80adm/domains/ossodomain/logs/server.log |
Verify that the certificate used for SSL communication is the root CA certificate.
Log out of the osso1.sp-example.com host machine.
Log in to the osso2.sp-example.com host machine as a root user.
Create a new user with roleadd.
# roleadd -s /sbin/sh -m -g staff -d /export/osso80adm osso80adm |
(Optional) Verify that the user was created.
# cat /etc/passwd root:x:0:0:Super-User:/:/sbin/sh daemon:x:1:1::/: ... nobody4:x:65534:65534:SunOS 4.x NFS Anonymous Access User:/: osso80adm:x:223830:10::/export/osso80adm:/sbin/sh |
(Optional) Verify that the user's directory was created.
# cd /export/osso80adm # ls local.cshrc local.profile local.login |
Create a password for the non-root user.
# passwd osso80adm New Password: nonroot2pwd Re-ener new Pasword: nonroot2pwd passwd: password successfully changed for osso80adm |
If you do not perform this step, you will not be able to switch user (su) when logged in as the non-root user.
Install Application Server and the appropriate CA root and CA-signed server certificates.
This procedure assumes you have just completed To Create a Non-Root User on the OpenSSO Enterprise 2 Host Machine and are still logged into the osso2.sp-example.com host machine as a root user.
Create a directory into which the Application Server bits can be downloaded and change into it.
# mkdir /export/AS91 # cd /export/AS91 |
Download the Sun Java System Application Server 9.1 Update 2 binary from the Sun Microsystems Product Download page to the AS91 directory of the osso2.sp-example.com host machine.
Grant the downloaded binary execute permission using the chmod command.
# chmod +x sjsas-9_1_02-solaris-sparc-ml.bin |
Install the software.
# ./sjsas-9_1_02-solaris-sparc-ml.bin -console |
When prompted, provide the following information.
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Press Enter to continue. |
|
|
Press Enter to display the Software License Agreement. |
|
|
Type yes and press Enter. |
|
|
Enter /opt/SUNWappserver91 |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the default value. |
|
|
Enter domain1pwd and then re-enter domain1pwd. |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the three default values. |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the default value. |
|
|
Press Enter to accept the default value and begin the installation process. |
|
|
When installation is complete, an Installation Successful message is displayed: |
|
|
Press Enter to exit the installation program. |
Create a second Application Server domain for the non-root user.
The default domain created during the installation process is owned by root. We create a new domain for osso80adm, the non-root user, into which we will deploy OpenSSO Enterprise.
# cd /opt/SUNWappserver91/bin # su osso80adm # ./asadmin create-domain --domaindir /export/osso80adm/domains --adminport 8989 --user domain2adm --instanceport 1080 --domainproperties http.ssl.port=1081 ossodomain Please enter the admin password> domain2pwd Please enter the admin password again> domain2pwd Please enter the master password [Enter to accept the default]:> domain2master Please enter the master password again [Enter to accept the default]:> domain2master Using port 8989 for Admin. Using port 1080 for HTTP Instance. Using default port 7676 for JMS. Using default port 3700 for IIOP. Using port 1081 for HTTP_SSL. Using default port 3820 for IIOP_SSL. Using default port 3920 for IIOP_MUTUALAUTH. Using default port 8686 for JMX_ADMIN. Domain being created with profile:developer, as specified by variable AS_ADMIN_PROFILE in configuration file. Security Store uses: JKS 2008-09-14 18:21:15.907 GMT Thread[main,5,main] java.io.FileNotFoundException: derby.log (Permission denied) ------------------------------------------------- 2008-09-14 18:21:16.216 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.1 - (538595): instance c013800d-0118-e205-d50b-00000c0c0770 on database directory /export/osso80adm/domains/ossodomain/lib/databases/ejbtimer Database Class Loader started - derby.database.classpath='' Domain ossodomain created. |
Creating a non-root domain displays a FileNotFoundException. Please see Appendix G, Known Issues and Limitations.
Verify that the non-root user domain was created with the correct permissions using the following sub-procedure.
Change to the ossodomain directory.
# cd /export/osso80adm/domains/ossodomain |
List the contents of the directory.
# ls -la total 30 drwxr-xr-x 15 osso80adm staff 512 Sep 14 16:43 . drwxr-xr-x 3 osso80adm staff 512 Sep 14 16:43 .. drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 addons drwxr-xr-x 6 osso80adm staff 512 Sep 14 16:43 applications drwxr-xr-x 3 osso80adm staff 512 Sep 14 16:43 autodeploy drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 bin drwx------ 3 osso80adm staff 1024 Sep 14 16:43 config drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 docroot drwxr-xr-x 6 osso80adm staff 512 Sep 14 16:43 generated drwxr-xr-x 3 osso80adm staff 512 Sep 14 16:43 imq drwxr-xr-x 5 osso80adm staff 512 Sep 14 16:43 java-web-start drwxr-xr-x 8 osso80adm staff 512 Sep 14 16:43 jbi drwxr-xr-x 6 osso80adm staff 512 Sep 14 16:43 lib drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 logs drwxr-xr-x 2 osso80adm staff 512 Sep 14 16:43 session-store |
The files and directories are owned by osso80adm.
Start ossodomain, the non-root user domain, using the following sub-procedure.
Verify that ossodomain has started with the following sub-procedure.
Access http://osso2.sp-example.com:8989/login.jsf from a web browser.
Log in to the Application Server console as the ossodomain administrator.
domain2adm
domain2pwd
When the Application Server administration console is displayed, it is verification that the non-root user was able to start the domain server.
Exit the console and close the browser.
Create a request for a CA-signed server certificate to secure communications between the soon-to-be-configured OpenSSO Enterprise load balancer and ossodomain using the following sub-procedure.
Generate a private/public key pair and reference it with the alias, opensso-sp-2.
opensso-sp-2 will be used in a later step to retrieve the public key which is contained in a self-signed certificate.
# cd /export/osso80adm/domains/ossodomain/config # keytool -genkey -noprompt -keyalg rsa -keypass domain2master -alias opensso-sp-2 -keystore keystore.jks -dname "CN=osso2.sp-example.com, OU=OpenSSO, O=Sun Microsystems, L=Santa Clara, ST=California, C=US" -storepass domain2master |
Verify that the key pair was successfully created and stored in the certificate store.
# keytool -list -v -keystore keystore.jks -storepass domain2master Keystore type: jks Keystore provider: SUN Your keystore contains two entries. ... ... Alias name: opensso-sp-2 Creation date: Sep 14, 2008 Entry type: keyEntry Certificate chain length: 1 Certificate[1]: Owner: CN=osso2.sp-example.com, OU=OpenSSO, O=Sun Microsystems, L=Santa Clara, ST=California, C=US Issuer: CN=osso2.sp-example.com, OU=OpenSSO, O=Sun Microsystems, L=Santa Clara, ST=California, C=US Serial number: 48cdb299 Valid from: Sun Sep 14 15:02:47 PDT 2008 until: Sat Dec 13 15:02:47 PDT 2008 Certificate fingerprints: MD5: 14:0F:88:BC:C8:6F:2C:8B:F0:A2:C2:F1:AF:FC:93:F1: SHA1: 9D:22:05:14:51:21:33:CB:06:36:25:FE:0A:B6:DF:45:EE:B1:19:86: |
The output of this command may list more than one certificate based on the entries in the keystore.
Generate a CA-signed server certificate request.
# keytool -certreq -alias opensso-sp-2 -keypass domain2master -keystore keystore.jks -storepass domain2master file opensso-sp-2.csr |
opensso-sp-2.csr is the server certificate request.
(Optional) Verify that opensso-sp-2.csr was created.
# ls -la opensso-sp-2.csr -rw-r--r-- 1 osso80adm staff 715 Sep 14 15:04 opensso-sp-2.csr |
Send opensso-sp-2.csr to the CA of your choice.
The CA issues and returns a certified certificate named opensso-sp-2.cer.
Import ca.cer, the CA root certificate.
The root certificate must be imported into two keystores (keystore.jks and cacerts.jks) with Application Server. Use the same root certificate that you imported in 7.4 Enabling Secure Communication for the Directory Server User Data Instances. For more information, see 3.3 Obtaining Secure Socket Layer Certificates.
# keytool -import -trustcacerts -alias OpenSSLTestCA -file ca.cer -keystore keystore.jks -storepass domain2master Owner: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=am, O=sun, L=santa clara, ST=california, C=us Issuer: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=am, O=sun, L=santa clara, ST=california, C=us Serial number: f59cd13935f5f498 Valid from: Thu Sep 20 11:41:51 PDT 2007 until: Thu Jun 17 11:41:51 PDT 2010 Certificate fingerprints: MD5: 78:7D:F0:04:8A:5B:5D:63:F5:EC:5B:21:14:9C:8A:B9 SHA1: A4:27:8A:B0:45:7A:EE:16:31:DC:E5:32:46:61:9E:B8:A3:20:8C:BA Trust this certificate? [no]: Yes Certificate was added to keystore |
# keytool -import -trustcacerts -alias OpenSSLTestCA -file ca.cer -keystore cacerts.jks -storepass domain2master Owner: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=am, O=sun, L=santa clara, ST=california, C=us Issuer: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=am, O=sun, L=santa clara, ST=california, C=us Serial number: f59cd13935f5f498 Valid from: Thu Sep 20 11:41:51 PDT 2007 until: Thu Jun 17 11:41:51 PDT 2010 Certificate fingerprints: MD5: 78:7D:F0:04:8A:5B:5D:63:F5:EC:5B:21:14:9C:8A:B9 SHA1: A4:27:8A:B0:45:7A:EE:16:31:DC:E5:32:46:61:9E:B8:A3:20:8C:BA Trust this certificate? [no]: Yes Certificate was added to keystore |
Replace the self-signed public key certificate (associated with the s1as alias) with the CA-signed server certificate.
# keytool -import -file opensso-sp-2.cer -alias opensso-sp-2 -keystore keystore.jks -storepass domain2master Certificate reply was installed in keystore |
(Optional) Verify that the self-signed public key certificate has been overwritten by the CA-signed server certificate.
# keytool -list -v -keystore keystore.jks -storepass domain2master The certificate indicated by the alias "opensso-sp-2" is signed by CA. |
Change the certificate alias from the default s1as to the new opensso-sp-2 in the domain.xml file for the ossodomain domain.
The Application Server configuration file is domain.xml.
<http-listener acceptor-threads="1" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-2" port="1081" security-enabled="true" server-name="" xpowered-by="true"> <ssl cert-nickname="opensso-sp-2" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true"/>
Backup domain.xml before modifying it.
Modify the JVM options in your web container's configuration file using the following sub-procedure.
OpenSSO Enterprise is deployed with an embedded configuration data store (if desired). In order for the configuration data store to be created successfully, the following JVM options should be modified in the web container's configuration file. We will be modifying domain.xml again for this example.
Backup domain.xml before modifying it.
Change to the config directory.
# cd /export/osso80adm/domains/ossodomain/config |
Open domain.xml in a text editor and make the following changes:
Replace <jvm-options>-client</jvm-options> with <jvm-options>-server</jvm-options>.
Replace <jvm-options>-Xmx512m</jvm-options> with <jvm-options>-Xmx1024m</jvm-options>.
Save the file and close it.
Restart the ossodomain domain.
# cd /export/osso80adm/domains/ossodomain/bin # ./stopserv Server was successfully stopped. ./startserv admin username:domain2adm admin password:domain2pwd master password:domain2master Redirecting output to /export/osso80adm/domains/ossodomain/logs/server.log |
Verify that the certificate used for SSL communication is the root CA certificate.
Log out of the osso2.sp-example.com host machine.
The two instances of OpenSSO Enterprise are fronted by one load balancer (Load Balancer 2). Users will access OpenSSO Enterprise through the secure port 1081. Load Balancer 2 sends the user and agent requests to the server where the session originated. Secure Sockets Layer (SSL) is terminated and regenerated before a request is forwarded to the OpenSSO Enterprise servers to allow the load balancer to inspect the traffic for proper routing. Load Balancer 2 is capable of the following types of load balancing:
Cookie-based |
The load balancer makes decisions based on client's cookies. The load balancer looks at the request and detects the presence of a cookie by a specific name. If the cookie is detected in the request, the load balancer routes the request to the specific server to which the cookie has been assigned. If the cookie is not detected in the request, the load balancer balances client requests among the available servers. |
IP-based |
This is similar to cookie-based load balancing, but the decision is based on the IP address of the client. The load balancer sends all requests from a specific IP address to the same server. |
TCP |
The load balancer mainstreams session affinity. This means that all requests related to a TCP session, are forwarded to the same server. In this deployment example, Load Balancer 2 forwards all requests from a single client to exactly the same server. When the session is started and maintained by one client, session affinity is guaranteed. This type of load-balancing is applicable to the TCP-based protocols. |
This section assumes that you have already installed a load balancer. Before you begin, note the following:
The load balancer hardware and software used in the lab facility for this deployment is BIG-IP® manufactured by F5 Networks. If you are using different load balancer software, see the documentation that comes with that product for detailed settings information.
Contact your network administrator to obtain an available virtual IP address for the load balancer you want to configure.
Know the IP address of the load balancer hardware, the URL for the load balancer login page, and a username and password for logging in to the load balancer application.
Get the IP addresses for OpenSSO Enterprise 1 and OpenSSO Enterprise 2 by running the following command on each host machine:
# ifconfig -a |
Use the following list of procedures as a checklist for completing the task.
To Request a Certificate for OpenSSO Enterprise Load Balancer 2
To Install a CA Root Certificate to OpenSSO Enterprise Load Balancer 2
To Install the Server Certificate to OpenSSO Enterprise Load Balancer 2
To Create an SSL Proxy for SSL Termination at the OpenSSO Enterprise Load Balancer 2
You should already have a root certificate from the CA of your choice. Generate a request for a server certificate to send to the CA. For more information, see 3.3 Obtaining Secure Socket Layer Certificates.
Access https://is-f5.siroe.com, the BIG-IP load balancer login page, in a web browser.
Log in to the BIG-IP console as the administrator.
Click Configure your BIG-IP (R) using the Configuration Utility.
In the left pane, click Proxies.
Click the Cert-Admin tab.
On the SSL Certificate Administration page, click Generate New Key Pair/Certificate Request.
In the Create Certificate Request page, provide the following information.
lb2.sp-example.com
Deployment
lb2.sp-example.com
password
password
Click Generate Key Pair/Certificate Request.
On the SSL Certificate Request page, the request is generated in the Certificate Request field.
Save the text contained in the Certificate Request field to a file named lb-2.csr.
Log out of the console and close the browser.
Send lb-2.csr to the CA of your choice.
The CA issues and returns a signed server certificate named lb-2.cer.
Install the CA root certificate on Load Balancer 2 to ensure that a link between it and the CA can be maintained. Use the same root certificate that you imported in 7.4 Enabling Secure Communication for the Directory Server User Data Instances. For more information, see 3.3 Obtaining Secure Socket Layer Certificates.
Access https://is-f5.example.com, the BIG-IP load balancer login page, in a web browser.
Log in to the BIG-IP console as the administrator.
In the BIG-IP load balancer console, click Proxies.
Click the Cert-Admin tab.
Click Import.
In the Import Type field, choose Certificate, and click Continue.
Click Browse in the Certificate File field on the Install SSL Certificate page.
In the Choose File dialog, choose Browser.
Navigate to ca.cer and click Open.
In the Certificate Identifier field, enter openSSLCA.
Click Install Certificate.
On the Certificate openSSLCA page, click Return to Certificate Administration.
The root certificate named openSSLCA is now included in the Certificate ID list.
This procedure assumes you have received the CA-signed server certificate requested in To Request a Certificate for OpenSSO Enterprise Load Balancer 2, just completed To Install a CA Root Certificate to OpenSSO Enterprise Load Balancer 2, and are still logged into the load balancer console.
In the BIG-IP load balancer console, click Proxies.
Click the Cert-Admin tab.
The key lb2.sp-example.com is in the Key List.
In the Certificate ID column, click Install for lb2.sp-example.com.
In the Certificate File field, click Browse.
In the Choose File dialog, navigate to lb-2.cer, the CA-signed server certificate, and click Open.
Click Install Certificate.
On the Certificate lb2.sp-example.com page, click Return to Certificate Administration Information.
Verify that the Certificate ID indicates lb2.sp-example.com on the SSL Certificate Administration page.
Log out of the load balancer console.
Access https://is-f5.example.com, the BIG-IP load balancer login page, in a web browser.
Log in to the BIG-IP console as the administrator.
Click Configure your BIG-IP (R) using the Configuration Utility.
Create a Pool.
A pool contains all the backend server instances.
In the left pane, click Pools.
On the Pools tab, click Add.
In the Add Pool dialog, provide the following information.
OpenSSO-SP-Pool
Round Robin
Add the IP addresses and port numbers for both OpenSSO Enterprise host machines.
Use port number 1081.
Click Done.
Add a Virtual Server.
The virtual server presents an address to the outside world and, when users attempt to connect, it would forward the connection to the most appropriate real server.
If you encounter JavaScriptTM errors or otherwise cannot proceed to create a virtual server, try using Internet Explorer.
In the left frame, click Virtual Servers.
On the Virtual Servers tab, click Add.
In the Add a Virtual Server dialog box, provide the following information:
Enter the IP address for lb2.sp-example.com
1082
Continue to click Next until you reach the Pool Selection dialog box.
In the Pool Selection dialog box, assign the OpenSSO-SP-Pool Pool.
Click Done.
Add Monitors.
OpenSSO Enterprise comes with a JSP file named isAlive.jsp that can be contacted to determine if the server is down. Since we have not yet deployed OpenSSO Enterprise, isAlive.jsp cannot be used. In the following sub procedure, create a custom monitor that periodically accesses the Application Server instance(s). If desired, the monitor can be changed later to use isAlive.jsp.
Click the Monitors tab
Click the Basic Associations tab
Find the IP address for osso1.sp-example.com:1080 and osso2.sp-example.com:1080.
Mark the Add checkbox that corresponds to the IP address for both osso1.sp-example.com:1080 and osso2.sp-example.com:1080.
At the top of the Node column, choose the tcp monitor.
Click Apply.
Configure the load balancer for persistence.
In the left pane, click BIGpipe.
In the BIGpipe command window, type the following:
makecookie ip-address:port |
ip-address is the IP address of the osso1.sp-example.com host machine and port is the same machine's port number; in this case, 1081.
Press Enter to execute the command.
Something similar to Set-Cookie: BIGipServer[poolname]=692589248.36895.0000; path=/ is displayed. Save the numbered value (in this case, 692589248.88888.0000) for use in To Create a Site on OpenSSO Enterprise 1.
In the left pane, click BIGpipe again.
In the BIGpipe command window, type the following:
makecookie ip-address:port |
ip-address is the IP address of the osso2.sp-example.com host machine and port is the same machine's port number; in this case, 1081.
Press Enter to execute the command.
Something similar to Set-Cookie: BIGipServer[poolname]=692589248.12345.0000; path=/ is displayed. Save the numbered value (in this case, 692589248.99999.0000) for use in To Create a Site on OpenSSO Enterprise 1.
Log out of the load balancer console.
SSL communication is terminated at Load Balancer 2. The request is then re-encrypted and securely forwarded to OpenSSO Enterprise. When clients send an SSL-encrypted request to Load Balancer 2, it decrypts the request and re-encrypts it before sending it on to the OpenSSO Enterprise SSL port. Load Balancer 2 also encrypts the responses it receives back from OpenSSO Enterprise, and sends these encrypted responses back to the client. Towards this end create an SSL proxy for SSL termination and regeneration.
Use the same root certificate that you imported in 7.4 Enabling Secure Communication for the Directory Server User Data Instances. For more information, see 3.3 Obtaining Secure Socket Layer Certificates.
Access https://is-f5.example.com, the BIG-IP load balancer login page, in a web browser.
Log in to the BIG-IP console as the administrator.
Click Configure your BIG-IP (R) using the Configuration Utility.
In the left pane, click Proxies.
Under the Proxies tab, click Add.
In the Add Proxy dialog, provide the following information.
Check the SSL and ServerSSL checkbox.
The IP address of Load Balancer 2.
1081
The secure port number
The IP address of Load Balancer 2.
1082
The non-secure port number
Choose Local Virtual Server.
Choose lb2.sp-example.com.
Choose lb2.sp-example.com.
Check this checkbox.
Click Next.
On the page starting with “Insert HTTP Header String,” change to Rewrite Redirects and choose Matching.
Click Next.
On the page starting with “Server Chain File,” change to Server Trusted CA's File, select “ca.cer” from the drop-down list.
Click Done.
The new proxy server is added to the Proxy Server list.
Log out of the load balancer console.
Access https://lb2.sp-example.com:1081/index.html from a web browser.
If the Application Server index page is displayed, you can access it using the new proxy server port number and the load balancer is configured properly.
A message may be displayed indicating that the browser doesn't recognize the certificate issuer. If this happens, install the CA root certificate in the browser so that the browser recognizes the certificate issuer. See your browser's online help system for information on installing a root CA certificate.
Close the browser.
An OpenSSO Enterprise WAR will be deployed in the installed Application Server containers on both OpenSSO Enterprise host machines. Additionally, you will configure the deployed applications. Use the following list of procedures as a checklist for completing the tasks.
To Generate an OpenSSO Enterprise WAR on the OpenSSO Enterprise 1 Host Machine
To Deploy the OpenSSO Enterprise WAR as OpenSSO Enterprise 1
To Copy the OpenSSO Enterprise WAR to the OpenSSO Enterprise 2 Host Machine
To Deploy the OpenSSO Enterprise WAR File as OpenSSO Enterprise 2
As a root user, log in to the osso1.sp-example.com host machine.
Create a directory into which the OpenSSO Enterprise ZIP file can be downloaded and change into it.
# mkdir /export/OSSO_BITS # cd /export/OSSO_BITS |
Download the OpenSSO Enterprise ZIP file from http://www.sun.com/download/.
Unzip the downloaded file.
# unzip opensso_enterprise_80.zip # cd /export/OSSO_BITS/opensso # ls -al total 68 drwxr-xr-x 14 root root 512 Sep 8 11:13 ./ drwxrwxr-x 3 root root 512 Sep 15 13:06 ../ -rw-r--r-- 1 root root 1349 Sep 8 10:58 README drwxr-xr-x 6 root root 512 Sep 8 11:15 deployable-war/ drwxr-xr-x 2 root root 512 Sep 8 11:13 docs/ drwxr-xr-x 2 root root 512 Sep 8 11:13 fedlet/ drwxr-xr-x 5 root root 512 Sep 8 11:11 integrations/ drwxr-xr-x 2 root root 512 Sep 8 11:13 ldif/ drwxr-xr-x 4 root root 512 Sep 8 11:13 libraries/ -rw-r--r-- 1 root root 17003 Sep 8 10:58 license.txt drwxr-xr-x 2 root root 512 Sep 8 11:13 migration/ drwxr-xr-x 2 root root 512 Sep 8 11:13 patches/ drwxr-xr-x 2 root root 512 Sep 8 11:13 samples/ drwxr-xr-x 2 root root 512 Sep 8 11:14 tools/ drwxr-xr-x 8 root root 512 Sep 8 11:13 upgrade/ drwxr-xr-x 2 root root 2048 Sep 8 11:11 xml/ |
|
Switch to the non-root user.
# su osso80adm |
Create a staging area in the non-root user directory into which the WAR will be exploded.
# cd /export/osso80adm # mkdir osso-staging |
In the staging area, after exploding the WAR, you can modify the WAR contents to suit your needs, generate a new WAR, and deploy it on any number of remote host computers. Whenever you need to make changes to the WAR, you maintain the changes in this one staging area, and redeploy the modified WAR as many times as you want, on as many host machines as you need.
Explode the WAR file.
# cd osso-staging # jar xvf /export/OSSO_BITS/opensso/deployable-war/opensso.war |
Make the following modifications to the bootstrap.properties file.
By default, during the WAR deployment, OpenSSO Enterprise creates a bootstrap file in the user's home directory. The bootstrap.properties file points to the directory where all the OpenSSO Enterprise configurations will be created. With these modifications, OpenSSO Enterprise will create the bootstrap file in the directory you specify; in this case, /export/osso80adm/config. bootstrap.properties is located in /export/osso80adm/osso-staging/WEB-INF/classes.
Uncomment the line that reads #configuration.dir=.
Add the following value to the configuration.dir= property so it reads as follows.
configuration.dir=/export/osso80adm/config |
Regenerate the WAR.
# cd /export/osso80adm/osso-staging # jar cvf ../opensso.war * |
A new WAR file is created, including the modified bootstrap.properties.
Verify that the new WAR was created in the proper location and with the appropriate permissions.
# cd /export/osso80adm/osso-staging # /bin/rm -rf * # jar xvf ../opensso.war # ls -al total 498 drwxr-xr-x 7 osso80adm staff 512 Aug 5 13:44 . drwxr-xr-x 12 root sys 512 Aug 5 11:11 .. -rw------- 1 osso80adm staff 779 Aug 5 14:56 .asadmintruststore drwx------ 2 osso80adm staff 512 Aug 5 14:44 .gconf drwx------ 2 osso80adm staff 512 Aug 5 14:44 .gconfd -rw-r--r-- 1 osso80adm staff 144 Aug 5 17:02 .profile drwx------ 3 osso80adm staff 512 Aug 5 11:20 .sunw drwxr-xr-x 3 osso80adm staff 512 Aug 5 14:55 domains drwxr-xr-x 21 osso80adm staff 1024 Aug 5 13:43 osso-staging -rw-r--r-- 1 osso80adm staff 68884903 Aug 5 13:45 opensso.war -rw-r--r-- 1 osso80adm staff 136 Aug 5 17:02 local.cshrc -rw-r--r-- 1 osso80adm staff 157 Aug 5 17:02 local.login -rw-r--r-- 1 osso80adm staff 174 Aug 5 17:02 local.profile |
The opensso.war file is owned by osso80adm.
This procedure assumes you have just completed To Generate an OpenSSO Enterprise WAR on the OpenSSO Enterprise 1 Host Machine and are still logged into the osso1.sp-example.com host machine
On the osso1.sp-example.com host machine, switch to the non-root user osso80adm.
# /bin/su osso80adm |
Start the ossodomain domain.
# cd /export/osso80adm/domains/ossodomain/bin # ./startserv admin username:domain2adm admin password:domain2pwd master password:domain2master Redirecting output to /export/osso80adm/domains/ossodomain/logs/server.log |
Run asadmin deploy to deploy the OpenSSO Enterprise WAR.
# cd /opt/SUNWappserver91/bin # ./asadmin deploy --user domain2adm --host osso1.sp-example.com --port=8989 --contextroot opensso --name opensso --target server /export/osso80adm/opensso.war Please enter the admin password> domain2pwd Command deploy executed successfully. |
List the contents of the j2ee-modules directory to verify that the WAR file was successfully deployed.
# cd /export/osso80adm/domains/ossodomain/applications/j2ee-modules # ls -al total 6 drwxr-xr-x 3 osso80adm staff 512 Aug 5 14:01 . drwxr-xr-x 6 osso80adm staff 512 Aug 5 14:55 .. drwxr-xr-x 21 osso80adm staff 1024 Aug 5 14:01 opensso |
opensso exists in the directory and is owned by the non-root user osso80adm.
Log out of the osso1.sp-example.com host machine.
This procedure assumes you have completed To Generate an OpenSSO Enterprise WAR on the OpenSSO Enterprise 1 Host Machine.
As a root user, log in to the osso2.sp-example.com host machine.
Switch to the non-root user osso80adm.
# /bin/su osso80adm |
Change into the osso80adm directory.
# cd /export/osso80adm |
Copy opensso.war from the osso1.sp-example.com host machine to the osso80adm directory.
Verify that the WAR file was copied into the proper location and with the appropriate permissions.
# ls -al total 130552 drwxr-xr-x 6 osso80adm staff 512 Sep 5 14:14 . drwxr-xr-x 8 root sys 512 Sep 5 10:54 .. -rw-r--r-- 1 osso80adm staff 70 Sep 5 14:13 .asadminpass -rw------- 1 osso80adm staff 778 Sep 5 14:12 .asadmintruststore drwx------ 2 osso80adm staff 512 Sep 5 13:15 .gconf drwx------ 2 osso80adm staff 512 Sep 5 13:26 .gconfd -rw-r--r-- 1 osso80adm staff 144 Sep 5 15:00 .profile drwx------ 3 osso80adm staff 512 Sep 5 15:26 .sunw drwxr-xr-x 3 osso80adm staff 512 Sep 5 14:12 domains -rw-r--r-- 1 osso80adm staff 68884903 Sep 5 14:14 opensso.war -rw-r--r-- 1 osso80adm staff 136 Sep 5 15:00 local.cshrc -rw-r--r-- 1 osso80adm staff 157 Sep 5 15:00 local.login -rw-r--r-- 1 osso80adm staff 174 Sep 5 15:00 local.profile |
opensso.war exists in the directory and is owned by osso80adm.
This procedure assumes you have just completed To Copy the OpenSSO Enterprise WAR to the OpenSSO Enterprise 2 Host Machine and are still logged into the osso2.sp-example.com host machine
On the osso2.sp-example.com host machine, switch to the non-root user osso80adm.
# /bin/su osso80adm |
Start the ossodomain domain.
# cd /export/osso8/domains/ossodomain/bin # ./startserv admin username:domain2adm admin password:domain2pwd master password:domain2master Redirecting output to /export/osso80adm/domains/ossodomain/logs/server.log |
Run asadmin deploy to deploy the OpenSSO Enterprise WAR file.
# cd /opt/SUNWappserver91/bin # ./asadmin deploy --user domain2adm --host osso2.sp-example.com --port=8989 --contextroot opensso --name opensso --target server /export/osso80adm/opensso.war Please enter the admin password> domain2pwd Command deploy executed successfully. |
List the contents of the j2ee-modules directory to verify that the WAR file was successfully deployed.
# cd /export/osso80adm/domains/ossodomain/applications/j2ee-modules # ls -al total 6 drwxr-xr-x 3 osso80adm staff 512 Sep 5 14:01 . drwxr-xr-x 6 osso80adm staff 512 Sep 5 14:55 .. drwxr-xr-x 21 osso80adm staff 1024 Sep 5 14:01 opensso |
opensso exists in the directory and is owned by the non-root user osso80adm.
Log out of the osso2.sp-example.com host machine.
Access https://osso1.sp-example.com:1081/opensso from a web browser.
The OpenSSO Enterprise Configurator page is displayed for first time access.
Select Create New Configuration under Custom Configuration on the Configurator page.
The OpenSSO Enterprise Custom Configuration Wizard is displayed.
Provide the following information for the Default User [amAdmin] in Step 1: General and click Next.
ossoadmin
ossoadmin
Accept the default values in Step 2: Server Settings and click Next
Do the following in Step 3: Configuration Store and click Next
Select Remote Directory in Step 4: User Store Settings, provide the following information and click Next
Check the box.
lb2.sp-example.com
489
o=spusers.com
dsmanager
Select Generic LDAP.
Select No in Step 5: Site Configuration and click Next.
Provide the following information for the Default Agent User [amldapuser] in Step 6: Default Agent User and click Next.
agentuser
agentuser
Click Create Configuration on the Summary page.
The Configuration Complete page is displayed after configuration is completed.
Click Proceed to Login on the Configuration Complete page.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
If authentication succeeds and the OpenSSO Enterprise console is displayed, OpenSSO Enterprise has successfully accessed the embedded configuration data store.
(Optional) To verify that the config directory and the supporting bootstrap directory have been created with the proper permissions, do the following.
As a root user, log in to the osso1.sp-example.com host machine.
Examine the file system.
# cd /export/osso80adm # ls -al total 130556 drwxr-xr-x 8 osso80adm staff 512 Sep 6 19:32 . drwxr-xr-x 14 root sys 512 Sep 6 09:07 .. -rw-r--r-- 1 osso80adm staff 70 Sep 27 14:01 .asadminpass -rw------- 1 osso80adm staff 1527 Sep 6 18:27 .asadmintruststore -rw-r--r-- 1 osso80adm staff 144 Sep 11 17:02 .profile drwx------ 3 osso80adm staff 512 Sep 24 11:20 .sunw drwxr-xr-x 4 osso80adm staff 512 Sep 6 19:34 config drwxr-xr-x 4 osso80adm staff 512 Sep 6 18:26 domains -rw-r--r-- 1 osso80adm staff 136 Sep 11 17:02 local.cshrc -rw-r--r-- 1 osso80adm staff 157 Sep 11 17:02 local.login -rw-r--r-- 1 osso80adm staff 174 Sep 11 17:02 local.profile |
The config directory was created and is owned by non-root user osso80adm.
Log out of the osso1.sp-example.com host machine.
Access https://osso2.sp-example.com:1081/opensso from a web browser.
The OpenSSO Enterprise Configurator page is displayed for first time access.
Select Create New Configuration under Custom Configuration on the Configurator page.
The OpenSSO Enterprise Custom Configuration Wizard is displayed.
Provide the following information for the Default User [amAdmin] in Step 1: General and click Next.
ossoadmin
ossoadmin
Accept the default values in Step 2: Server Settings and click Next
Do the following in Step 3: Configuration Store and click Next
Select No in Step 5: Site Configuration and click Next.
Click Create Configuration on the Summary page.
The Configuration Complete page is displayed after configuration is completed.
Click Proceed to Login on the Configuration Complete page.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
If authentication succeeds and the OpenSSO Enterprise console is displayed, OpenSSO Enterprise has successfully accessed the embedded configuration data store.
(Optional) To verify that the config directory and the supporting bootstrap directory have been created with the proper permissions, do the following.
As a root user, log in to the osso2.sp-example.com host machine.
Examine the file system.
# cd /export/osso80adm # ls -al total 130556 drwxr-xr-x 8 osso80adm staff 512 Aug 6 19:32 . drwxr-xr-x 14 root sys 512 Aug 6 09:07 .. -rw-r--r-- 1 osso80adm staff 70 Mar 27 14:01 .asadminpass -rw------- 1 osso80adm staff 1527 Aug 6 18:27 .asadmintruststore -rw-r--r-- 1 osso80adm staff 144 Mar 11 17:02 .profile drwx------ 3 osso80adm staff 512 Mar 24 11:20 .sunw drwxr-xr-x 4 osso80adm staff 512 Aug 6 19:34 config drwxr-xr-x 4 osso80adm staff 512 Aug 6 18:26 domains -rw-r--r-- 1 osso80adm staff 136 Mar 11 17:02 local.cshrc -rw-r--r-- 1 osso80adm staff 157 Mar 11 17:02 local.login -rw-r--r-- 1 osso80adm staff 174 Mar 11 17:02 local.profile |
The config directory was created and is owned by non-root user osso80adm.
Log out of the osso2.sp-example.com host machine.
The Platform Service provides centralized configuration management for an OpenSSO Enterprise deployment. In this procedure, you configure the two OpenSSO Enterprise servers to work as a single unit. Once configured as a site, all client requests go through the configured load balancer. Use the following list of procedures as a checklist for completing this task.
It is not necessary to repeat this procedure on OpenSSO Enterprise 2.
Access https://osso1.sp-example.com:1081/opensso/console in a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Under the Configuration tab, click Servers and Sites.
The Servers and Sites page is displayed.
Click New under Sites.
The New Site properties page is displayed.
Enter the following values for the load balancer and click OK.
sp-site
https://lb2.sp-example.com:1081/opensso
A new site called sp-site is displayed in the Sites list.
Click on the https://osso1.sp-example.com:1081/opensso server entry under the Servers list.
The Edit https://osso1.sp-example.com:1081/opensso page is displayed.
Assign sp-site from the Parent Site drop down list and click Save.
Click the Advanced tab.
Enter the number generated for the osso1.sp-example.com host machine as the value of the com.iplanet.am.lbcookie.value property and click Save.
The number was generated using the makecookie command in To Configure OpenSSO Enterprise Load Balancer 2.
Click Back to Server and Sites.
Click on the https://osso2.sp-example.com:1081/opensso server entry under the Servers list.
The Edit https://osso2.sp-example.com:1081/opensso page is displayed.
Assign sp-site from the Parent Site drop down list and click Save.
Click the Advanced tab.
Enter the number generated for the osso2.sp-example.com host machine as the value of the com.iplanet.am.lbcookie.value property and click Save.
The number was generated using the makecookie command in To Configure OpenSSO Enterprise Load Balancer 2.
Click Back to Server and Sites.
You should see sp-site under the Site Name column for both servers.
Log out of the OpenSSO Enterprise console.
As a root user, log in to the osso1.sp-example.com host machine.
Restart OpenSSO Enterprise for the changes to take effect.
# /bin/su osso80adm # cd /export/osso80adm/domains/ossodomain/bin # ./stopserv; ./startserv Server was successfully stopped. admin username: domain2adm admin password: domain2pwd master password: domain2master Redirecting output to /export/osso80adm/domains/ossodomain/logs/server.log |
As a root user, log in to the osso2.sp-example.com host machine.
Restart the web container for the changes to take effect.
# /bin/su osso80adm # cd /export/osso80adm/domains/ossodomain/bin # ./stopserv; ./startserv Server was successfully stopped. admin username: domain2adm admin password: domain2pwd master password: domain2master Redirecting output to /export/osso80adm/domains/ossodomain/logs/server.log |
Log out of both OpenSSO Enterprise host machines.
Access the load balancer at https://lb2.sp-example.com:1081/opensso/UI/Login.
If an error message is displayed indicating that the browser cannot connect to either osso1.sp-example.com or osso2.sp-example.com, the site configuration is not correct. If the site configuration is correct, all browser interactions will occur as expected.
When the OpenSSO Enterprise login page is displayed, verify that the browser URL still contains the Primary Site URL for the load balancer.
If it does not contain the Site URL, the site configuration is incorrect. If the site configuration is correct, all browser interactions will occur through the secure Site URL.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
A successful login occurs when the site configuration is correct.
Log out of the OpenSSO Enterprise console.
Configure OpenSSO Enterprise on the service provider side to recognize the Directory Server LDAP schema previously modified for SAML v2 attributes.
This procedure assumes you have completed 7.3 Modifying the Directory Server Schema.
Access https://lb4.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
The Common Tasks tab is displayed.
Click the Access Control tab and / (Top-level Realm) on the Access Control page.
Click the Data Stores tab.
Under the Data Stores tab, click embedded.
The Generic LDAPv3 page is displayed.
Add the following values to properties on the Generic LDAPv3 page.
Type sunFMSAML2NameIdentifier in the New Value box of the LDAP User Object Class property and click Add.
Add the following values to the LDAP User Attribute property.
Type sun-fm-saml2-nameid-infokey in the New Value box and click Add.
Type sun-fm-saml2-nameid-info in the New Value box and click Add.
Click Save on the Generic LDAPv3 page.
Log out of the OpenSSO Enterprise console.
This chapter contains instructions on configuring OpenSSO Enterprise to use the external user data store (set up in Chapter 4, Installing Sun Java System Directory Server and Creating Instances for User Data) for authentication credentials. This is done by modifying the top-level realm or, alternately, configuring a sub realm for the external users and creating an authentication chain. Choose either of the sections listed to configure OpenSSO Enterprise for user authentication.
Do not do both.
At this point in the deployment, the root realm (by default, / (Top Level Realm)) is configured to authenticate special OpenSSO Enterprise accounts (for example, amadmin and agents) against the embedded configuration data store. Since the external user data store is an instance of Directory Server and not part of the embedded configuration data store, we modify the configuration details of the top-level realm to include the user data stores schema, allowing OpenSSO Enterprise to recognize users in the external user data store. Use the following list of procedures as a checklist for completing this task.
Access https://osso1.sp-example.com:1081/opensso/console in a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Click the Access Control tab.
Click / (Top Level Realm), the root realm, under the Access Control tab.
Click the Data Stores tab.
The embedded data store link is displayed.
Click embedded.
The Generic LDAPv3 properties page is displayed.
On the Generic LDAPv3 properties page, set the following attribute values and click Save.
Enter ou.
Enter Groups.
Enter ou.
Enter users.
If this field is empty, the search for user entries will start from the root suffix.
Click Back to Data Stores.
(Optional) Click the Subjects tab to verify that the test users are now displayed.
spuser is displayed under Users (as well as others created during OpenSSO Enterprise configuration).
Click the Authentication tab.
Click the Advanced Properties link under General.
The Core Realm Attributes page is displayed.
Change the value of User Profile to Ignored.
This new value specifies that a user profile is not required by the Authentication Service in order to issue a token after successful authentication. This modification is specific to this deployment example because the OpenSSO Enterprise schema and the Directory Server schema have not been mapped.
Click Save.
Click Back to Authentication.
Click Back to Access Control.
Log out of the OpenSSO Enterprise console.
You should be able to log in successfully as the test user.
Access https://osso1.sp-example.com:1081/opensso/UI/Login in a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
spuser
spuser
You should be able to log in successfully and see a page with a message that reads You're logged in. Since the User Profile attribute was previously set to Ignored, the user's profile is not displayed after a successful login. If the login is not successful, watch the Directory Server access log to troubleshoot the problem.
At this point in the deployment, / (Top Level Realm), the root realm, is configured to authenticate special OpenSSO Enterprise accounts (for example, amadmin and agents) against the embedded configuration data store. Since the external user data store is an instance of Directory Server and not part of the embedded configuration data store, we create a sub realm and modify the configuration details to include the external user data stores schema, allowing OpenSSO Enterprise to recognize users in the Directory Server instances. The sub realm creates a demarcation between OpenSSO Enterprise configuration and administrative data and the user data. Use the following list of procedures as a checklist for completing this task.
To Verify That the Sub Realm Can Access the External User Data Store
To Verify That the Sub Realm Subjects Can Successfully Authenticate
When a sub realm is created it inherits configuration data (including which user data store to access) from the root realm (by default, / (Top Level Realm)) and uses said data to authenticate users. The user data store can be modified per sub realm. In this deployment, we use the inherited Generic LDAPv3 data store.
Access https://osso1.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Click the Access Control tab.
Click New to create a new realm.
The New Realm page is displayed.
Set the following attribute values on the New Realm page.
Enter users.
Enter users in the New Value field and click Add.
Click OK.
The users realm is listed as a sub realm of / (Top Level Realm), the root realm.
This procedure assumes you have just completed To Create a Sub Realm and are still logged in to the OpenSSO Enterprise console.
Under the Access Control tab, click the users realm.
Click the Authentication tab.
Click the Advanced Properties link under General.
The Core Realm Attributes page is displayed.
Change the value of User Profile to Ignored.
This new value specifies that a user profile is not required by the Authentication Service in order to issue a token after successful authentication.
Click Save.
Click Back to Access Control.
This procedure assumes you have just completed To Change the User Profile Configuration for the Sub Realm and are still logged in to the OpenSSO Enterprise console.
Click users, the sub realm, under the Access Control tab.
Click the Data Stores tab.
The embedded data store link is displayed.
Click embedded.
The Generic LDAPv3 properties page is displayed.
On the Generic LDAPv3 properties page, set the following attribute values and click Save.
Enter ou.
Enter Groups.
Enter ou.
Enter users.
If this field is empty, the search for user entries will start from the root suffix.
Click Back to Data Stores.
(Optional) Click the Subjects tab to verify that the test users are now displayed.
spuser is displayed under Users (as well as others created during OpenSSO Enterprise configuration).
Log out of the OpenSSO Enterprise console.
This optional procedure is to verify the modifications.
Access https://osso1.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Click on the Access Control tab
Click on the users sub realm.
Click on the Subjects tab.
idpuser is displayed under Users.
Log out of the OpenSSO Enterprise console.
Access https://osso1.sp-example.com:1081/opensso/UI/Login?realm=users from a web browser.
The parameter realm=users specifies the realm to use for authentication. At this point, a user can log in against Directory Server only if the realm parameter is defined in the URL.
Log in to OpenSSO Enterprise with as a test user.
spuser
spuser
You should be able to log in successfully and see a page with a message that reads You're logged in. Since the User Profile attribute was set to Ignored, the user's profile is not displayed after a successful login. If the login is not successful, watch the Directory Server access log to troubleshoot the problem.
In this deployment, protected resources are hosted on one machine that contains two installed web containers (one Sun Java™ System Web Server and one BEA WebLogic Server application server) and the appropriate policy agent for each (a web policy agent and a J2EE policy agent, respectively). The policy agents are configured to access the OpenSSO Enterprise Load Balancer 4. This chapter contains the following sections:
10.1 Installing the J2EE Container and J2EE Policy Agent on Protected Resource 1
10.2 Installing the Web Server and Web Policy Agent on Protected Resource 1
Download the BEA WebLogic Server bits to the Protected Resource 1 host machine (pr1.sp-example.com) and install the application server. Additionally, download, install and configure the appropriate J2EE policy agent. Use the following list of procedures as a checklist for completing this task.
To Import a Certificate Authority Root Certificate to Protected Resource 1
To Deploy and Start the J2EE Policy Agent Housekeeping Application
To Configure the J2EE Policy Agent to Bypass Application Server Administrator Authentication
To Configure the J2EE Policy Agent for SAML v2 Communication
BEA WebLogic Server is the application server used as the J2EE web container on Protected Resource 1.
Ensure that your machine is properly patched. Refer to the BEA web site to make sure that your system has the recommended patches.
As a root user, log into the pr1.sp-example.com host machine.
Create a directory into which you can download the WebLogic Server bits and change into it.
# mkdir /export/BEAWL10 # cd /export/BEAWL10 |
Download the WebLogic Server bits from http://commerce.bea.com/.
For this deployment, we download the Solaris version.
# ls -al total 294548 drwxr-xr-x 2 root root 512 Aug 7 13:23 . drwxr-xr-x 3 root sys 512 Aug 7 13:16 .. -rw-r--r-- 1 root root 656834948 Aug 7 13:24 server100_solaris32.bin |
Run the installer.
# ./server100_solaris32.bin |
When prompted, do the following:
|
Click Next. |
|
|
Select Yes and click Next. |
|
|
Type /usr/local/bea and click Next. |
|
|
Click Next. |
|
|
Click Next. |
|
|
Type /usr/local/bea/weblogic10 and click Next. |
|
|
Deselect Run Quickstart and click Done. |
(Optional) Verify that the application was correctly installed.
# cd /usr/local/bea # ls -al total 90 drwxr-xr-x 7 root root 512 Jul 15 11:59 . drwxr-xr-x 4 root root 512 Jul 15 11:58 .. -rwxr-xr-x 1 root root 826 Jul 15 11:59 UpdateLicense.sh -rw-r--r-- 1 root root 14 Jul 15 11:59 beahomelist drwxr-xr-x 6 root root 512 Jul 15 11:59 jdk150_06 -rw-r--r-- 1 root root 12447 Jul 15 11:59 license.bea drwxr-xr-x 2 root root 512 Jul 15 11:59 logs drwxr-xr-x 6 root root 6656 Jul 15 11:58 modules -rw-r--r-- 1 root root 15194 Jul 15 11:59 registry.dat -rw-r--r-- 1 root root 1077 Jul 15 11:59 registry.xml drwxr-xr-x 4 root root 512 Jul 15 12:01 utils drwxr-xr-x 10 root root 512 Jul 15 11:59 weblogic10 |
This procedure assumes you have just completed To Install BEA WebLogic Server on Protected Resource 1 and are still logged into the host machine as the root user.
Run the WebLogic Server configuration script.
# cd /usr/local/bea/weblogic10/common/bin # ./config.sh |
When prompted, do the following:
Start AdminServer, the WebLogic administration server.
# cd /usr/local/bea/user_projects/domains/pr1 # ./startWebLogic.sh |
When prompted, type the following credentials.
weblogic
bea10admin
Run the netstat command to verify that the port is open and listening.
# netstat -an | grep 7001 XXX.XX.XX.101.7001 *.* 0 0 49152 0 LISTEN XXX.X.X.1.7001 *.* 0 0 49152 0 LISTEN |
You can also access the administration console by pointing a web browser to http://pr1.sp-example.com:7001/console.
Change to the AdminServer directory.
# cd /usr/local/bea/user_projects/domains/pr1/servers/AdminServer |
Create a security directory and change into it.
# mkdir security # cd security |
Create a boot.properties file for the WebLogic Server administration server administrator credentials.
The administration server administrative user and password are stored in boot.properties. Application Server 1 uses this information during startup. WebLogic Server encrypts the file, so there is no security risk even if you enter the user name and password in clear text.
# cat > boot.properties username=weblogic password=bea10admin Hit Control D to terminate the command ^D |
Restart WebLogic to encrypt the username and password in boot.properties.
# cd /usr/local/bea/user_projects/domains/pr1/bin # ./stopWebLogic.sh # ./startWebLogic.sh |
Start the managed servers.
# cd /usr/local/bea/user_projects/domains/pr1/bin # ./startManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001 |
You will be prompted for the administrative user credentials.
weblogic
bea10admin
Change to the ApplicationServer-1 directory.
# cd /usr/local/bea/user_projects/domains/pr1/ servers/ApplicationServer-1 |
Create a security directory and change into it.
# mkdir security # cd security |
Create a boot.properties file for the WebLogic Server managed server administrator credentials.
The managed server administrative user and password are stored in boot.properties. The Application Server 1 managed server uses this information during startup. WebLogic Server encrypts the file, so there is no security risk even if you enter the user name and password in clear text.
# cat > boot.properties username=weblogic password=bea10admin Hit Control D to terminate the command ^D |
Restart the managed server.
# cd /usr/local/bea/user_projects/domains/ pr-1/bin # ./stopManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001 # ./startManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001 |
Run the netstat command to verify that the port is open and listening.
# netstat -an | grep 1081 XXX.XX.XX.101.1081 *.* 0 0 49152 0 LISTEN XXX.X.X.1.1081 *.* 0 0 49152 0 LISTEN |
Access http://pr1.sp-example.com:7001/console from a web browser.
Login to the BEA WebLogic Server as the administrator.
weblogic
bea10admin
Click servers under Domain Structure —>Environment.
On the Summary of Servers page, verify that both AdminServer (admin) and ApplicationServer-1 are running and OK.
Log out of the console.
Log out of the pr1.sp-example.com host machine.
The Certificate Authority (CA) root certificate enables the J2EE policy agent to trust the certificate from the OpenSSO Enterprise Load Balancer 2, and to establish trust with the certificate chain that is formed from the CA to the certificate.
Copy the same CA root certificate used in To Install a CA Root Certificate to OpenSSO Enterprise Load Balancer 2 to the /export/software directory on the pr1.sp-example.com host machine.
As a root user, log into the pr1.sp-example.com host machine.
Change to the directory where cacerts, the certificate store is located.
# cd /usr/local/bea/jdk150_06/jre/lib/security. |
Backup cacerts before modifying it.
Import ca.cer, the CA root certificate.
# /usr/local/bea/jdk150_06/bin/keytool -import -trustcacerts -alias OpenSSLTestCA -file /export/software/ca.cer -keystore /usr/local/bea/jdk150_06/jre/lib/security/cacerts -storepass changeit Owner: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=Sun, O=Sun,L=Santa Clara, ST=California C=US Issuer: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=Sun, O=Sun,L=Santa Clara, ST=California C=US Serial number: 97dba0aa26db6386 Valid from: Tue Apr 18 07:66:19 PDT 2006 until: Tue Jan 13 06:55:19 PST 2009 Certificate fingerprints: MD5: 9f:57:ED:B2:F2:88:B6:E8:0F:1E:08:72:CF:70:32:06 SHA1: 31:26:46:15:C5:12:5D:29:46:2A:60:A1:E5:9E:26:64:36:80:E4:70 Trust this certificate: [no] yes Certificate was added to keystore. |
Verify that ca.cer was successfully imported.
# /usr/local/bea/jdk150_06/bin/keytool -list -keystore /usr/local/bea/jdk150_06/jre/lib/security/cacerts -storepass changeit | grep -i openssl OpenSSLTestCA, Sep 15, 2008, trustedCertEntry, |
Log out of the pr1 host machine.
Set JAVA_HOME to /usr/local/bea/jdk150_06.
As a root user, log into the pr1.sp-example.com host machine.
Stop the WebLogic Server 1 administration server and the WebLogic Server 1 managed instance.
# cd /usr/local/bea/user_projects/domains/pr1/bin # ./stopManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001 # ./stopWebLogic.sh |
Create a directory into which you will download the J2EE Policy Agent bits and change into it.
# mkdir /export/J2EEPA1 # cd /export/J2EEPA1 |
Create a text file that contains a password for the Agent Profile created during installation.
The J2EE Policy Agent installer requires this.
# cat > agent.pwd j2eeagent1 Hit Control D to terminate the command ^D |
Download the J2EE policy agent bits for WebLogic Server from http://www.sun.com/download/index.jsp.
# ls -al total 18824 drwxr-xr-x 2 root root 512 Jul 17 16:02 . drwxr-xr-x 8 root root 512 Jul 17 15:58 .. -rw-r--r-- 1 root root 11 Jul 17 15:59 agent.pwd -rw-r--r-- 1 root root 9 Jul 17 16:01 agentadm.pwd -rw-r--r-- 1 root root 9623704 Jul 17 16:02 weblogic_v10_agent_3.zip |
Unzip the J2EE policy agent bits.
# unzip weblogic_v10_agent_3.zip |
Run the J2EE policy agent installer.
# cd /export/J2EEPA1/j2ee_agents/weblogic_v10_agent/bin # chmod 755 agentadmin # ./agentadmin --custom-install |
When prompted, provide the following information.
The following information is to configure the J2EE Policy Agent against the OpenSSO Enterprise secure port.
|
Press Enter to continue. Continue to press Enter until you reach the end of the License Agreement and the installer's Welcome page is displayed. |
|
|
Enter /usr/local/bea/user_projects/domains/pr1/bin/startwebLogic.sh |
|
|
Enter the name of the WebLogic Server instance secured by the agent ApplicationServer-1 |
|
|
Enter /usr/local/bea/weblogic10. |
|
|
Enter the URL where OpenSSO Enterprise is running (including the URI): https://lb4.sp-example.com:1081/opensso |
|
|
Accept the default value. |
|
|
Enter the URL where the policy agent is running (including the URI): http://pr1.sp-example.com:1081/agentapp |
|
|
Accept the default value. |
|
|
j2eeagent-1 |
|
|
Enter /export/J2EEPA1/agent.pwd, path to the file that contains the password used for identifying the policy agent. Note – A warning message is displayed regarding the existence of the agent profile. |
|
|
Accept the default value to create the Agent Profile during installation. |
|
|
Accept the default value. |
|
|
Accept the default value. |
When the installer is finished, a new file is in the bin directory called setAgentEnv_ApplicationServer-1.sh.
Modify the startup script setDomainEnv.sh to reference setAgentEnv_ApplicationServer-1.sh with the following sub procedure.
Backup setDomainEnv.sh before you modify it.
Change permissions for setAgentEnv_ApplicationServer-1.sh.
# chmod 755 setAgentEnv_ApplicationServer-1.sh |
Start the WebLogic Server administration server and managed instance.
# ./startWebLogic.sh & # ./startManagedWebLogic.sh ApplicationSever-1 t3://localhost:7001 |
Watch for startup errors.
Verify that the J2EE Policy Agent 1 was successfully created in OpenSSO Enterprise using the following sub procedure.
Access https://lb4.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Under the Access Control tab, click / (Top Level Realm).
Click the Agents tab.
Click the J2EE tab.
j2eeagent-1 is displayed under the Agent table.
Click j2eeagent-1.
The j2eeagent-1 properties page is displayed.
Log out of the OpenSSO Enterprise console and close the browser.
Remove the password files.
# cd /export/J2EEPA1 # rm agent.pwd # rm agentadm.pwd |
Log out of the pr1.sp-example.com host machine.
The agent application is a housekeeping application bundled with the binaries and used by the agent for notifications and other internal functionality. This application must be deployed to the agent-protected web container using the same URI that was supplied during the agent installation process. For example, during the installation process, if you entered /agentapp as the deployment URI for the agent application, use that same context path in this procedure.
Access http://pr1.sp-example.com:7001/console from a web browser.
Log in to the WebLogic Server console as the administrator.
weblogic
bea10admin
Under Domain Structure, click Deployments.
On the Summary of Deployments page, in the Change Center, click Lock & Edit.
Under Deployments, click Install.
On the Install Application Assistant page, click the pr1.sp-example.com link.
In the field named Location: pr1.sp-example.com, click the root directory.
Navigate to /export/J2EEPA1/j2ee_agents/weblogic_v10_agent/etc, the application directory.
Select agentapp.war and click Next.
In the Install Application Assistant page, choose Install this deployment as an application and click Next.
In the list of Servers, mark the checkbox for ApplicationServer-1 and click Next.
In the Optional Settings page, click Next.
Click Finish.
On the Settings for agentapp page, click Save.
In the Change Center, click Activate Changes.
On the Settings for agentapp page, click Deployments.
On the Summary of Deployments page, mark the agentapp checkbox and click Start > Servicing all requests.
On the Start Application Assistant page, click Yes.
If you encounter a JavaScriptTM error, start the WebLogic Server instance and perform the steps again.
Access Application Server 1 at http://pr1.sp-example.com:7001/console.
Log in to the WebLogic Server console as the administrator.
weblogic
bea10admin
On the Change Center, click Lock & Edit.
Under Domain Structure, click Deployments.
Under Deployments, click Install.
On the Install Application Assistant page, click the pr1.sp-example.com link.
In the list for Location: pr1.example.com, click the root directory.
Navigate to the application directory (/export/J2EEPA1/j2ee_agents/weblogic_v10_agent/sampleapp/dist), select agentsample.ear and click Next.
In the Install Application Assistant page, choose Install this deployment as an application and click Next.
In the list of Servers, mark the checkbox for ApplicationServer-1 and click Next.
On the Optional Settings page, click Next to accept the default settings.
On the Review Your Choices page, click Finish.
The Target Summary section indicates that the module agentsample will be installed on the target ApplicationServer-1.
On the Settings for agentsample page, click Save.
On the Settings for agentsample page, click Activate Changes.
Under Domain Structure, click Deployments.
In the Deployments list, mark the checkbox for agentsample and click Start > Servicing All Requests.
On the Start Application Assistant page, click Yes.
The state of the deployment changes from Prepared to Active.
Log out of the Application Server 1 console.
The J2EE policy agent can operate in local or centralized mode. The centralized option was selected during the custom installation of the agent. Centralized agent configuration stores agent configuration data in a data store managed by OpenSSO Enterprise. Since J2EE policy agents are configured in centralized mode, any configuration changes must be made using the OpenSSO Enterprise server. In this procedure, configure the agent to bypass authentication of the Application Server administrator.
Access https://lb4.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Under the Access Control tab, click / (Top Level Realm).
Click the Agents tab.
Click the J2EE tab.
j2eeagent-1 is displayed under the Agent table.
Click j2eeagent-1.
The j2eeagent-1 properties page is displayed.
Click the Miscellaneous tab.
The Miscellaneous properties page is displayed.
Provide the user name of the Application Server administrator in the Bypass Principal List and click Add.
Enter weblogic to ensure that the administrator will be authenticated against WebLogic itself and not OpenSSO Enterprise.
Click Save.
Exit the console and close the browser.
Access https://lb4.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Under the Access Control tab, click / (Top Level Realm).
Click the Agents tab.
Click the J2EE tab.
j2eeagent-1 is displayed under the Agent table.
Click j2eeagent-1.
The j2eeagent-1 properties page is displayed.
Click the General link on the j2eeagent-1 properties page.
Remove the existing value of the Agent Filter Mode property.
This value is displayed in the Current Values text box.
Add the following values to the New Value text boxes and click Add.
agentsample
SSO_ONLY
Click Save.
Log out of the OpenSSO Enterprise console and close the browser.
Log in to the pr1.sp-example.com host machine as root user.
Restart the WebLogic administration server and managed instance.
# cd /usr/local/bea/user_projects/domains/pr1/bin # ./stopManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001 # ./stopWebLogic.sh # ./startWebLogic.sh # ./startManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001 |
Log out of the pr1.sp-example.com host machine.
Verify the configurations with the following sub procedure.
Close and reopen the browser application.
Access http://pr1.sp-example.com:1081/agentsample from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
spuser
spuser
The user is redirected to the service provider console for authentication.
Close the browser.
Access https://lb4.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Under the Access Control tab, click / (Top Level Realm).
Click the Agents tab.
Click the J2EE tab.
j2eeagent-1 is displayed under the Agent table.
Click j2eeagent-1.
The j2eeagent-1 properties page is displayed.
Click the OpenSSO Services tab.
The Edit j2eeagent-1 page is displayed.
Click the Login URL link on the Edit j2eeagent-1 page.
Remove the existing value of the OpenSSO Login URL property.
This value is displayed in the Selected box.
Enter https://lb4.sp-example.com:1081/opensso/spssoinit? metaAlias=/sp&idpEntityID=https://lb2.idp-example.com:1181/opensso in the text box and click Add.
This URL redirects the agent to the identity provider for authentication.
Enter https://lb4.sp-example.com:1081/opensso/saml2/jsp/spSingleLogoutInit.jsp?idpEntityID=https://lb2.idp-example.com:1181/opensso as a value of the OpenSSO Logout URL attribute and click Add.
Click Save.
Click the Application tab.
Add the following values to the Application Logout URI text boxes and click Add.
agentsample
/agentsample/logout
Click Save.
Log out of the OpenSSO Enterprise console and close the browser.
Log in to the pr1.sp-example.com host machine.
Restart the WebLogic administration server and managed instance.
# cd /usr/local/bea/user_projects/domains/pr1/bin # ./stopManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001 # ./stopWebLogic.sh # ./startWebLogic.sh # ./startManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001 |
Log out of the pr1.sp-example.com host machine.
Verify the configurations with the following sub procedure.
Access http://pr1.sp-example.com:1081/agentsample from a web browser.
The user is redirected to the OpenSSO Enterprise login page on the identity provider side.
Log in to the OpenSSO Enterprise console as the administrator.
idpuser
idpuser
After successful authentication, single sign on is accomplished between the identity provider and the service provider.
Access http://pr1.sp-example.com:1081/agentsample/logout from a web browser.
The J2EE policy agent sample application welcome page is displayed. The user has successfully logged out of both the identity provider and the service provider.
Download the Sun Java System Web Server bits to the Protected Resource 1 host machine (pr1.sp-example.com) and install it. Additionally, download, install and configure the appropriate web policy agent. Use the following list of procedures as a checklist for completing the task.
To Install and Configure Sun Java System Web Server on Protected Resource 1
To Import a Certificate Authority Root Certificate to Protected Resource 1
To Install and Configure Web Policy Agent on Protected Resource 1
Sun Java System Web Server is the second web container used on the pr1.sp-example.com host machine.
Read the latest version of the Web Server 7.0 Release Notes to determine if you need to install patches on your host machine. In this case, the Release Notes indicate that based on the hardware and operating system being used, patch 119963–08, patch 120011–14, and patch 117461–08 are required.
As a root user, log into the pr1.sp-example.com host machine.
Run patchadd to see if the patch is installed.
# patchadd -p | grep 117461–08 |
A list of patch numbers is displayed. On our lab machine, the required patch 117461–08 is present so there is no need to install it.
# patchadd -p | grep 119963–08 |
No results are returned which indicates that the patch is not yet installed on the system.
# patchadd -p | grep 120011-14 |
No results are returned which indicates that the patch is not yet installed on the system.
Make a directory for downloading the patch you need and change into it.
# mkdir /export/patches # cd /export/patches |
Download the patches.
You can search for patches directly at http://sunsolve.sun.com. Navigate to the PatchFinder page, enter the patch number, click Find Patch, and download the appropriate patch.
Signed patches are downloaded as JAR files. Unsigned patches are downloaded as ZIP files.
Unzip the patch file.
# unzip 119963–08.zip # unzip 120011–14.zip |
Run patchadd to install the patches.
# patchadd /export/patches/119963–08 # patchadd /export/patches/120011–14 |
After installation is complete, run patchadd to verify that the patch was added successfully.
# patchadd -p | grep 119963–08 |
In this example, a series of patch numbers are displayed, and the patch 119963–08 is present.
# patchadd -p | grep 120011-14 |
In this example, a series of patch numbers are displayed, and the patch 120011–14 is present.
This procedure assumes you have just finished To Patch the Protected Resource 1 Host Machine and are still logged in as the root user.
Create a directory into which you can download the Web Server bits and change into it.
# mkdir /export/WS7 # cd /export/WS7 |
Download the Sun Java System Web Server 7.0 Update 3 software from http://www.sun.com/download/products.xml?id=45ad781d.
Follow the instructions on the Sun Microsystems Product Downloads web site for downloading the software.
Unpack the Web Server package.
# gunzip sjsws-7_0u3-solaris-sparc.tar.gz # tar xvf sjsws-7_0u3-solaris-sparc.tar |
Run setup.
# cd /export/WS7 # ./setup --console |
When prompted, provide the following information.
|
Press Enter. Continue to press Enter when prompted. |
|
|
Enter yes. |
|
|
Enter /opt/SUNWwbsvr |
|
|
Enter yes. |
|
|
Enter 2. |
|
|
Enter 1,3,5. |
|
|
Enter 1. |
|
|
Enter 1. |
|
|
Accept the default value. |
|
|
Accept the default value. |
|
|
Accept the default value. |
|
|
Enter no. |
|
|
Accept the default value (for the administration server). |
|
|
Accept the default value. |
|
|
Enter web4dmin. |
|
|
Enter web4dmin. |
|
|
Accept the default value. |
|
|
Enter 1080. |
|
|
Enter root (for the instance). |
|
|
Accept the default value. |
|
|
Enter no. |
|
|
Enter1. |
When installation is complete, the following message is displayed:
Installation Successful. |
Start the Web Server administration server.
# cd /opt/SUNWwbsvr/admin-server/bin # ./startserv |
Run netstat to verify that the port is open and listening.
# netstat -an | grep 8989 *.8989 *.* 0 0 49152 0 LISTEN |
(Optional) Login to the Web Server administration console at https://pr1.sp-example.com:8989 as the administrator.
admin
web4dmin
You should see the Web Server administration console.
(Optional) Log out of the Web Server console and close the browser.
Start the Protected Resource 1 Web Server instance.
# cd /opt/SUNWwbsvr/https-pr1.sp-example.com/bin # ./startserv Sun Java System Web Server 7.0U3 B06/16/2008 12:00 info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_15] from [Sun Microsystems Inc.] info: HTTP3072: http-listener-1: http://pr1.sp-example.com:1080 ready to accept requests info: CORE3274: successful server startup |
Run netstat to verify that the port is open and listening.
# netstat -an | grep 1080 *.1080 *.* 0 0 49152 0 LISTEN |
(Optional) Access the Protected Resource 1 instance at http://pr1.sp-example.com:1080 using a web browser.
You should see the default Web Server index page.
Log out of the pr1.sp-example.com host machine.
The Certificate Authority (CA) root certificate enables the web policy agent to trust the certificate from the OpenSSO Enterprise Load Balancer 2, and to trust the certificate chain that is formed from the CA to the server certificate.
Copy the same CA root certificate used in To Install a CA Root Certificate to OpenSSO Enterprise Load Balancer 2 to the pr1.sp-example.com host machine. In this example, the file is /export/software/ca.cer.
Backup cacerts before modifying it.
As a root user, log into the pr1.sp-example.com host machine.
Import the CA root certificate into cacerts, the certificate store.
# /opt/SUNWwbsvr/jdk/jre/bin/keytool -import -trustcacerts -alias OpenSSLTestCA -file /export/software/ca.cer -keystore /opt/SUNWwbsvr/jdk/jre/lib/security/cacerts -storepass changeit Owner: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=Sun, O=Sun,L=Santa Clara, ST=California C=US Issuer: EMAILADDRESS=nobody@nowhere.com, CN=OpenSSLTestCA, OU=Sun, O=Sun,L=Santa Clara, ST=California C=US Serial number: f59cd13935f5f498 Valid from: Thu Sep 20 11:14:51 PDT 2008 18 07:66:19 PDT 2006 until: Thu Jun 17 11:41:51 PDT 2010 Certificate fingerprints: MD5: 78:7D:F0:04:8A:5B:5D:63:F5:EC:5B:21:14:9C:8A:B9 SHA1: A4:27:8A:B0:45:7A:EE:16:31:DC:E5:32:46:61:9E:B8:A3:20:8C:BA Trust this certificate: [no] yes Certificate was added to keystore. |
Verify that the CA root certificate was imported.
# /opt/SUNWwbsvr/jdk/jre/bin/keytool -list -keystore /opt/SUNWwbsvr/jdk/jre/lib/security/cacerts -storepass changeit | grep -i open openSSLTestCA, Sep 20, 2008, trustedCertEntry, |
Log out of the pr1.sp-example.com host machine.
The JAVA_HOME environment variable should be set to /opt/SUNWwbsvr/jdk/jre.
As a root user, log into the pr1.sp-example.com host machine.
Create a directory into which you can download the Web Server agent bits and change into it.
# mkdir /export/WebPA1 # cd /export/WebPA1 |
Create a text file that contains the Agent Profile password.
The Web Policy Agent installer requires this for installation.
# cat > agent.pwd webagent1 Hit Control D to terminate the command ^D |
Download the web policy agent for Web Server from http://www.sun.com/download/.
# ls -al total 7512 drwxr-xr-x 2 root root 512 Jul 24 14:48 . drwxr-xr-x 11 root root 512 Jul 24 14:41 .. -rw-r--r-- 1 root root 10 Jul 24 14:42 agent.pwd -rw-r--r-- 1 root root 9 Jul 24 14:42 agentadm.pwd -rw-r--r-- 1 root root 3826794 Jul 24 14:48 sjsws_v70_SunOS_sparc_agent_3.zip |
Unzip the downloaded file.
# unzip sjsws_v70_SunOS_sparc_agent_3.zip |
Run the agent installer.
# cd /export/WebPA1/web_agents/sjsws_agent/bin # ./agentadmin --custom-install |
When prompted, do the following.
|
Press Enter and continue to press Enter until you have reached the end of the License Agreement. |
|
|
Type yes and press Enter. |
|
|
Type /opt/SUNWwbsvr/https-pr1.sp-example.com/config and press Enter. |
|
|
Type https://lb4.example.com:1081/opensso and press Enter. |
|
|
Type http://pr1.sp-example.com:1080 and press Enter. |
|
|
Accept the default value. |
|
|
Type webagent-1 and press Enter. |
|
|
Type /export/WebPA1/agent.pwd and press Enter. Note – A warning message is displayed regarding the existence of the agent profile. |
|
|
Type 1 and press Enter. |
Restart the Web Server 1 instance.
# cd /opt/SUNWwbsvr/https-pr1.sp-example.com/bin # ./stopserv; ./startserv server has been shutdown Sun Java System Web Server 7.0U3 B06/16/2008 12:00 info: CORE3016: daemon is running as super-user info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_15] from [Sun Microsystems Inc.] info: HTTP3072: http-listener-1: http://pr1.sp-example.com:1080 ready to accept requests info: CORE3274: successful server startup |
Verify that the Web Policy Agent was successfully created in OpenSSO Enterprise using the following sub procedure.
Access https://lb4.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Under the Access Control tab, click / (Top Level Realm).
Click the Agents tab.
By default, the Web tab is displayed. You should see webagent-1 under the Agent table.
Click webagent-1.
The webagent-1 properties page is displayed.
Log out of the console and close the browser.
Remove the password files.
# cd /export/WebPA1 # rm agent.pwd # rm agentadm.pwd |
Log out of the pr1.sp-example.com host machine.
Access https://lb4.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Under the Access Control tab, click / (Top Level Realm).
Click the Agents tab.
Click the Web tab.
webagent-1 is displayed under the Agent table.
Click webagent-1.
The webagent-1 properties page is displayed.
Click the General link on the webagent-1 properties page.
Select the check box to enable the SSO Mode Only property.
Click Save.
Log out of the OpenSSO Enterprise console and close the browser.
Log in to the pr1.sp-example.com host machine as root user.
Restart the Web Server.
# cd /opt/SUNWwbsvr/https-pr1.sp-example.com/bin # ./stopserv # ./startserv |
Log out of the pr1.sp-example.com host machine.
Verify the configurations with the following sub procedure.
Access https://lb4.sp-example.com:1081/opensso/console from a web browser.
Log in to the OpenSSO Enterprise console as the administrator.
amadmin
ossoadmin
Under the Access Control tab, click / (Top Level Realm).
Click the Agents tab.
Click the Web tab.
webagent-1 is displayed under the Agent table.
Click webagent-1.
The webagent-1 properties page is displayed.
Click the OpenSSO Services tab.
The Edit webagent-1 page is displayed.
Click the Login URL link on the Edit webagent-1 page.
Remove the existing value of the OpenSSO Login URL property.
This value is displayed in the Selected box.
Enter https://lb4.sp-example.com:1081/opensso/spssoinit?metaAlias=/sp&idpEntityID=https://lb2.idp-example.com:1181/opensso in the text box and click Add.
This URL redirects the agent to the identity provider for authentication.
Select the existing value of the OpenSSO Logout URL attribute and click Delete.
Enter https://lb4.sp-example.com:1081/opensso/saml2/jsp/spSingleLogoutInit.jsp?metaAlias=/sp&idpEntityID=https://lb2.idp-example.com:1181/opensso in the text box and click Add.
Enter http://www.sun.com as a value of the Logout Redirect URL attribute and click Add.
Enter http://pr1.sp-example.com:1080/logout.html as a value of the Agent Logout URL List attribute and click Add.
Click Save.
Log out of the OpenSSO Enterprise console and close the browser.
Log in to the pr1.sp-example.com host machine.
Create the logout.html file using the following sub procedure.
# cd /opt/SUNWwbsvr/https-pr1.sp-example.com/docs # vi logout.html |
This creates an empty file.
Restart the Web Server.
# cd /opt/SUNWwbsvr/https-pr1.sp-example.com/bin # ./stopserv # ./startserv |
Log out of the pr1.sp-example.com host machine.
Verify the configurations with the following sub procedure.
Access http://pr1.sp-example.com:1080/index.html from a web browser.
The OpenSSO Enterprise login page on the identity provider side is displayed. The browser is then redirected to the identity provider for authentication.
Log in to the OpenSSO Enterprise console using the following credentials.
idpuser
idpuser
The default Web Server page is displayed.
Access http://pr1.sp-example.com:1080/logout.html from a web browser.
This will log out the user from the service provider and the identity provider using the SAML v2 single logout protocol.
Close the browser.