<wss:KeyIdentifier ValueType="saml:Assertion" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" xmlns:wss="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">A ssertion-uuidf704fe86-0104-e0d9-428d-bc0b9265e970</wss:KeyIdentifier> </wss:SecurityTokenReference> </wst:RequestedAttachedReference> </wst:RequestSecurityTokenResponse> </soapenv:Body> </soapenv:Envelope> 10.5 Configuration data 10.5.1 Overall architecture and prerequisites The Interaction description shown in Figure 10-1, "Use case 4 logical architecture" on page 293 made use of a single WebSEAL instance and three WebSphere Application Server instances. The successful configuration of the scenario depends upon Tivoli Federated Identity Manager Web services security management and all of its prerequisite software having first been installed and configured on the WebSphere Application Servers according to the instructions in the Tivoli Federated Identity Manager Web services security management Guide.