Web Browser Artifact Profile Fails When SAML v2 Plug-in for Federation Services Patch 3 Installed on Federation Manager and WebSphere

When Federation Manager is deployed in WebSphere Application Server, federation using the Web Browser Artifact Profile fails when the service provider attempts to send an artifact back to the identity provider.

WORKAROUND: You must override WebSphere's default SOAP factory by doing the following:

1. Edit WebSphere's server.xml file (located in WebSphere-base/WebSphere/AppServer/config/cells/cell-name/nodes/node-name/servers/server-instance/) by replacing

   <jvmEntries xmi:id="JavaVirtualMachine_1" classpath="" 
   bootClasspath="" verboseModeClass="false" verboseModeGarbageCollection="false" 
   verboseModeJNI="false" runHProf="false" hprofArguments="" 
   debugMode="false" debugArgs="-Djava.compiler=NONE -Xdebug -Xnoagent 
   -Xrunjdwp:transport=dt_socket,server=y,suspend=n, address=7777" 
   genericJvmArguments="">

   with

   <jvmEntries xmi:id="JavaVirtualMachine_1" verboseModeClass="false" 
   verboseModeGarbageCollection="false" verboseModeJNI="false" 
   initialHeapSize="256" maximumHeapSize="256" runHProf="false" 
   hprofArguments="" debugMode="false" debugArgs="-Djava.compiler=NONE 
   -Xdebug -Xnoagent 
   -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777" 
   genericJvmArguments="-Dcom.iplanet.am.serverMode=true">
   <classpath>/usr/share/lib/saaj-api.jar:/usr/share/
   lib/saaj-impl.jar</classpath>

   ---

   Note –

   The cell-name, node-name, and server-instance variables identify the name of the cell, node, and server in which Federation Manager is deployed.

   ---

2. Restart the WebSphere instance.

6320498