Sun Java System SAML v2 Plug-in for Federation Services Release Notes

SAML v2 Plug-in for Federation Services Patch 3

The following versions of Patch 3 are now available from SunSolve. For information about applying these patches, see the rel_notes.html included inside the patch binary.


Caution – Caution –

The SAML v2 Plug-in for Federation Services Patch 3 can not be installed directly on Access Manager 7.0 or Federation Manager 7.0. You must first install the SAML v2 Plug-in for Federation Services product release, or already have an existing installation of the product release. Then, following the appropriate procedure, you can update your installation to Patch 3 for Solaris (SPARC and x86), Linux and Windows.


Table 1–3 SAML v2 Plug-in for Federation Services Patch 3 Numbers

Patch Number 

Operating System 

122983-03 

For instances of Access Manager 7 2005Q4 and Federation Manager 7.0 on Solaris operating system (SPARC) 

122984-03 

For instances of Access Manager 7 2005Q4 and Federation Manager 7.0 on Solaris operating system (x86) 

122985-03 

For instances of Access Manager 7 2005Q4 and Federation Manager 7.0 on Linux application environment 

126360-03 

For instances of Access Manager 7 2005Q4 and Federation Manager 7.0 on the Windows operating system 


Note –

The following issues are fixed when Patch 3 is installed:


Additional Information for Microsoft Windows Installations

The following information is applicable when installing the SAML v2 Plug-in for Federation Services on Microsoft Windows.

ProcedureSAML v2 Plug-in for Federation Services Patch 3 Windows Installation Notes

  1. Before installing the SAML v2 Plug-in for Federation Services Patch 3 on Windows, ensure that the LDAP server is running, and the web container is shutdown. The installer needs to modify files held by the web container process.

  2. When installing the SAML v2 Plug-in for Federation Services Patch 3 on Solaris and Linux, sample metadata templates and a circle of trust will be automatically created. This is not done when installing on Windows. To create metadata templates and a circle of trust on Windows after installation, start your web container and run saml2meta. See The saml2meta Command-line Reference in Sun Java System SAML v2 Plug-in for Federation Services User’s Guide for more information.

ProcedureTo Upgrade a SAML v2 Plug-in for Federation Services Windows Deployment on Access Manager 7.0 or Federation Manager 7.0 to Patch 3

Before You Begin

You should already have a staging directory from your initial installation. This variable is referred to as war staging dir in the following procedure.

  1. Download the Windows patch.

    See Table 1–3.

  2. Unzip the file into a new directory.

  3. Copy saml2.jar from unzip directory\saml2\lib to war staging dir\WEB-INF\lib.

  4. Change to the unzip directory\saml2\samples\useCaseDemo directory.

  5. Copy init.jspf to the war staging dir\samples\saml2\useCaseDemo.

    This action will overwrite the earlier init.jspf.

  6. Generate a new WAR from the war staging dir.

  7. Redeploy the new WAR to your web container.

ProcedureTo Cleanup a Failed SAML v2 Plug-in for Federation Services Patch 3 Windows Installation

It may be necessary to clean up an attempted installation of Patch 3 if an error is encountered. If this situation occurs, future attempts to install the patch will fail unless this procedure is followed.

  1. Remove the base_dir\saml2 directory.

    This directory contains the SAML v2 binary bits.

  2. Remove the following SAML v2 related properties from the bottom of AMConfig.properties.

    • com.sun.identity.saml2.am_or_fm

    • com.sun.identity.saml2.xmlenc.EncProviderImpl

    • com.sun.identity.saml2.xmlenc.SigProviderImpl

    • com.sun.identity.common.datastore.provider.default

  3. Remove the appropriate Access Manager or Federation Manager staging directory and extract new one.