SAML Assertion Request Has Two Timestamps Entries, Which Make The Receiver Throw A 500 Error (Doc ID 1562543.1)

Last updated on JULY 22, 2013

Applies to:

Oracle Workshop for Weblogic - Version 10.3 to 10.3 [Release AS10gR3]
Information in this document applies to any platform.

Symptoms

Weblogic workshop control(10.3.0) acts as a client side and the page flow calls the webservice (SAML Sender Vouches) in 10.3.0.

The issue is that SAML assertion request has two timestamps entries,which make the receiver throw a 500 error

This is being simulated under load doing 10+ WS calls with different users at the same time.

For the failed run,its as below

<wsse:Security>

   <wsse:BinarySecurityToken>...</wsse:BinarySecurityToken>

   <wsse:SecurityTokenReference>...</wsse:SecurityTokenReference>

   <wsse:SecurityTokenReference>...</wsse:SecurityTokenReference>

 

   <wsse:BinarySecurityToken>...</wsse:BinarySecurityToken>

   <wsse:SecurityTokenReference>...</wsse:SecurityTokenReference>

  <wsse:SecurityTokenReference>...</wsse:SecurityTokenReference>

 

   <wsu:Timestamp>

   <wsu:Timestamp>

</wsse:Security>

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms