Hi All,

Is this a know issue for salesforce? I am also getting the same timestamp #4 and Miscellaneous format confirmations error #6. I have checked both ADFS and SSO setting and they seems perfect.

Unexpected Exceptions
  Ok
1. Validating the Status
  Ok
2. Looking for an Authentication Statement
  Ok
3. Looking for a Conditions statement
  Ok
4. Checking that the timestamps in the assertion are valid
  Current time is after notOnOrAfter in Conditions
  Current time is: 2016-04-28T08:10:53.776Z
  Time limit in Conditions, adjusted for skew, is: 2016-04-27T15:51:39.705Z
  Timestamp of the response is outside of allowed time window
  Current time is: 2016-04-28T08:10:53.776Z
  Timestamp is: 2016-04-27T15:43:39.705Z
  Allowed skew in milliseconds is 480000
  Timestamp of the assertion is outside of allowed time window
  Current time is: 2016-04-28T08:10:53.776Z
  Timestamp is: 2016-04-27T15:43:39.705Z
  Allowed skew in milliseconds is 480000
5. Checking that the Attribute namespace matches, if provided
  Not Provided
6. Miscellaneous format confirmations
  InResponseTo must be empty for Idp-init Browser POST Profile
7. Confirming Issuer matches
  Ok
8. Confirming a Subject Confirmation was provided and contains valid timestamps
  Ok
9. Checking that the Audience matches
  Ok
10. Checking the Recipient
  Ok
  Organization Id that we expected: 00D36000000Yrhi
  Organization Id that we found based on your assertion: 00D36000000Yrhi
11. Validating the Signature
  Is the response signed? false
  Is the assertion signed? true
  Is the correct certificate supplied in the keyinfo? true
  Ok
12. Checking that the Site URL Attribute contains a valid site url, if provided
  Not Provided
13. Looking for portal and organization id, if provided
  Ok
14. Checking if session security level is valid, if provided
  Ok


Thanks in Advance.

​-Vikash Kumar

Hello.

 

We're working on an integration with ADFS and followed the document on developerForce to a T. We are getting some strange errors that I'm not sure how to troubleshoot. See below:

 

10. Checking the Recipient

  Organization Id that we expected: 00DU0000000XXXX

  Organization Id that we found based on your assertion: 00DU0000000XXXX

 

The OrgIDs above are exact matches. Not sure why this is displaying as an error.

 

4. Checking that the timestamps in the assertion are valid

  Current time is after notOnOrAfter in Conditions

  Current time is: 2012-02-16T22:00:12.184Z

  Time limit in Conditions, adjusted for skew, is: 2012-02-13T22:50:15.127Z

  Timestamp of the response is outside of allowed time window

  Current time is: 2012-02-16T22:00:12.184Z

  Timestamp is: 2012-02-13T22:42:15.125Z

  Allowed skew in milliseconds is 480000

  Timestamp of the assertion is outside of allowed time window

  Current time is: 2012-02-16T22:00:12.184Z

  Timestamp is: 2012-02-13T22:42:15.045Z

  Allowed skew in milliseconds is 480000

 

The time on the machine is exactly the same as the time in Salesforce, at least it is on the ActiveDirectory. Where is it getting the time from here?