Sun OpenSSO Enterprise 8.0 implements the Identity Provider Discovery profile (part of the SAMLv2 binding profiles) for its Identity Provider Discovery Service to keep track of the identity providers for each user. Deploying the IPP Discovery Service includes these steps:
To generate an IDP Discovery Service WAR file, use the jar command to extract the files from the opensso.war file and then to generate the specialized WAR file.
Download and unzip the opensso_enterprise_80.zip file. You will then need the following files:
zip-root/deployable-war/opensso.war is the OpenSSO Enterprise WAR file that contains all components, including the IDP Discovery Service files.
zip-root/deployable-war/fam-idpdiscovery.list specifies the files that are required to generate an IDP Discovery Service WAR file.
zip-root/deployable-war/idpdiscovery directory contains additional files you will need to deploy and configure the IDP Discovery Service.
where zip-root is where you unzipped the opensso_enterprise_80.zip file.
For more information about the opensso.war file, see Downloading OpenSSO Enterprise.
Make sure that your JAVA_HOME environment variable points to JDK 1.5 or later.
Create a new staging directory and extract the files from opensso.war in this staging directory. For example:
# mkdir idpdiscovery # cd idpdiscovery # jar xvf zip-root/opensso/deployable-war/opensso.war
Create the IDP Discovery Service WAR using the files in fam-idpdiscovery.list:
# cd idpdiscovery # jar cvf zip-root/opensso/deployable-war/idpdiscovery.war \ @zip-root/opensso/deployable-war/fam-idpdiscovery.list
where idpdiscovery.war is the name of the new IDP Discovery Service WAR file.
Update the idpdiscovery.war file created in previous step with the additional files required for the IDP Discovery Service. For example:
# cd zip-root/opensso/deployable-war/idpdiscovery # jar uvf zip-root/opensso/deployable-war/idpdiscovery.war *
You are now ready to configure the new idpdiscovery.war, as described in the next section.
OpenSSO Enterprise includes the IDP Discovery Service Configurator (Configurator.jsp) to configure the service.
Login as a user who has the following privileges:
Access to the web container administration console, if you plan to deploy idpdiscovery.war using this console.
The capability to execute the web container's deploy command-line utility, if you plan to deploy idpdiscovery.war using the CLI.
Deploy the idpdiscovery.war to the web container using either the web container administration console or CLI command.
Launch the Configurator using the following URL:
For example: http://idpdiscoveryhost.example.com:8080/idpdiscovery
If the IDP Discovery Service is not already configured, you will be directed to the Configurator page.
On the Configurator page, specify the following information:
Debug Level: error (default), warning, message, or off.
Cookie Type: PERSISTENT (default) or SESSION
Secure Cookie: True or False (default)
Encode Cookie: True (default) or False
On the SP host machine, use the console to create a Circle of Trust with the IDP Discovery Service URL used as the prefix for the value of the Reader and Writer URL attributes. For example:
SAML2 Writer Service URL: http://idp-discovery-server-machine:port/idpdiscovery/saml2writer
SAML2 Reader Service URL: http://idp-discovery-server-machine:port/idpdiscovery/saml2reader
On the IDP host machine, use the console to create a Circle of Trust with the value of the prefix attribute also set to the identity provider discovery service URL. For example:
Generate metadata for both the IDP and the SP using the ssoadm command-line utility with the create-metadata-templ option.
Load the SP metadata into the IDP machine.
Change the value of the host in the IDP metadata from 0 or remote.
Load the IDP metadata into the SP machine.
After this configuration, the values of the Writer URL and Reader URL in each Circle of Trust are the URL of the IDP Discovery Service.
Perform the SAMLv2 test cases for SP-initiated and IDP-initiated single sign-on and single logout. Each time you perform these operations from the SP side, the Discovery Service logs will show the redirection to the IDP.