Identity Provider could not process the authentication request received

[Former Member]

Hello,

We are getting the following error when opening a weblink via SAP SSO.

I am not an SAML expert hence appreciate your inputs in fixing this issue.

The following document was followed to set SSO -->

We are using a HANA XS system and using Java script.

The following 400 Bad Request error details are as below.

1. Request URL:https://accounts400.sap.com/saml2/idp/sso/accounts.sap.com?SAMLRequest=MIICEzCCAXygAwIBAgIETOp//zANB...
2. Request Method:GET
3. Status Code:400 Bad Request
4. Request Headersview source
   1. Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
   2. Accept-Encoding:gzip,deflate,sdch
   3. Accept-Language:en-US,en;q=0.8
   4. Cache-Control:max-age=0
   5. Connection:keep-alive
   6. Cookie:__gads=ID=e03c7847c08c5dee:T=1379071680:S=ALNI_Mb6u6_pm2FKxij2c3x3c76LZkWYag; shpuvid=rBBcnFI24hAMsQpVA2vSAg==; client=8ddbfa6f-1c67-11e3-ac19-391f31fa2cd0; __utma=33188028.507792856.1409214099.1412575636.1417168894.4; __utmz=33188028.1409214099.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _ga=GA1.2.507792856.1409214099; SAP.TTC=1417675977; session=2d7e89f4-7b82-11e4-bd26-016305f2e40b; ids=rd3o00000000000000000000ffffac107842o443; mbox=session#1418028758361-416095#1418031961|check#true#1418030161; s_pers=%20s_ttc%3D-%7C1449564997415%3B%20s_nr%3D1418030101560-Returning%7C1420622101560%3B%20s_fid%3D09B3E3251D0EF875-3E0A7FE459CB6279%7C1481188703997%3B%20gpv_p9%3DlogY%7C1418032104013%3B%20c13%3Dscn-jive%253Aglo%253Apost%2521input%7C1418032104013%3B%20pe%3Dno%2520value%7C1418032104013%3B%20c3%3Dnon-blog%2520page%2520view%7C1418032104013%3B%20s_sapvisid%3D8ddbfa6f1c6711e3ac19391f31fa2cd0%7C1547630304029%3B%20s_visit%3D1%7C1418032104029%3B; s_sess=%20c11%3Didentity%2520provider%2520could%2520not%2520process%2520the%2520authentication%2520request%2520received%3B%20s_cc%3Dtrue%3B%20s_sq%3Dsapcommunity%252Csapglobal%253D%252526pid%25253Dscn-jive%2525253Aglo%2525253Apost%25252521input%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Breturnfalse%2525253B%2525257D%252526oidt%25253D2%252526ot%25253DA%3B
   7. Host:accounts400.sap.com
5. User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
6. Query String Parametersview sourceview URL encoded
   1. SAMLRequest:MIICEzCCAXygAwIBAgIETOp//zANBgkqhkiG9w0BAQUFADBNMQswCQYDVQQGEwJERTEPMA0GA1UEBxMGQmVybGluMQwwCgYDVQQKEwNTQVAxDjAMBgNVBAsTBVdlYkttMQ8wDQYDVQQDEwZDUFMgUUEwIBcNMTAxMTIyMTQzNjQ3WhgPMjExMDEwMjkxNDM2NDdaME0xCzAJBgNVBAYTAkRFMQ8wDQYDVQQHEwZCZXJsaW4xDDAKBgNVBAoTA1NBUDEOMAwGA1UECxMFV2ViS20xDzANBgNVBAMTBkNQUyBRQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAjGCTddfUltkmYCpiB37R5r5TL0wqdm/DsrXt8CAExtygVfoQQM8avG duIWqWJHD8K5qpeYRI5GTSSqSMgZfdoqvbfH3EnUd2r2V3E4Eh26JTu0YXYG16xwN9NSXcKhfzCdYeQgsiYPA03sprnTEanQy8KF8B4eRihNK8RhYN4MCAwEAATANBgkqhkiG9w0BAQUFAAOBgQAk7eIJdFxiYLTUk4c/pW63k1L6QOVKgimR9RXDSeZwbP4gMytw3Eb6apyzd QUbp3UPD2MSLLKsLKO3VWEjAFbzJSRzSneilQDIMMyc8MT/PUdyXyoqGlmKFnH/mboaQiCd1oMlEy1MvnP6TWY5xh97Vsv3wmdLzV4W nFgW0gTQ
   2. Signature:MsZ06a/kUn0J15easoR WouHwAB8FP5kQ3yNLDKBWnlt/jANxSYMwsuI5/TixZWqwCQ4YpbYXNniMpZZp8SP0nwhBkn1rvnZf K95r/DDp7tB3WRHhpleBntsSf00L4IF3lgs/11hmdEaplqlejSET5DfZCoxnST1bR9WHzq7Ck
7. Response Headersview source
   1. Cache-Control:no-cache
   2. Cache-Control:no-store
   3. Content-Language:en-US
   4. Content-Length:1741
   5. Content-Type:text/html;charset=utf-8
   6. Date:Mon, 08 Dec 2014 09:20:49 GMT
   7. Expires:Thu, 01 Jan 1970 00:00:00 GMT
   8. P3P:CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
   9. Pragma:no-cache
   10. Server:SAP
   11. X-Cnection:close
   12. X-IDS-Node:mo-e2bce8dbf
   13. X-IDS-Pool:main_green
   14. X-IDS-Region:Europe
   15. 
       
   16. Looking forward to your response.
   17. 
       
   18. Thanks,
   19. Sanjiv
       
       
   20. 
       

[Former Member]

This has been resolved internally by our developers and IT team combined.

[Former Member]

Hello Sanjiv,

can you please give us a short hint what is required to fix the issue? We do exactly face the reported issue as well.

Is there a special implementation or configuration directly within the xs application required?

Best regards,

Tobias

[vijay_kumar49]

Did you clear the browser cache and stored cookies, and did you restart the your browse?

refer this document

[Former Member]

Hi Vijay,

I can't image how the browser cache or a stored cookies can lead into a "HTTP 400 bad request" error as we are talking about SAML usage to enable Single-Sign-On (SOO) within SAP HANA xs applications.

Best regards,

Tobias

[Former Member]

Hello Sanjiv,

was there any solution provided for this issue already?

Best regards,

Tobias