Trying to set up theTwo way SSL for Forex rate API. I have followed the steps mentioned in Starting guide and created a Java Keystore.
Trying to access hello world API using SOAP UI to verify the SSL communication on sandbox, but getting the below error, although providing user id and password as part of the basic authentication.
HTTP/1.1 400 Bad Request
X-SERVED-BY: l73c035
X-CORRELATION-ID: 1495205269_709_68_l73c035_VDP_ARM
X-APP-STATUS: 400
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=2592000;includeSubdomains
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Security-Policy-Report-Only: default-src 'self' https://*.v.me https://*.visa.com;script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.visa.com https://*.v.me;img-src 'self' https://*.v.me https://*.visa.com https://*.unica.com https://ad.doubleclick.net;style-src 'self' 'unsafe-inline' https://*.visa.com;object-src https://*.v.me https://*.visa.com data:;report-uri /logging/logCSPReport;
X-Content-Security-Policy-Report-Only: default-src 'self' https://*.v.me https://*.visa.com;script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.visa.com https://*.v.me;img-src 'self' https://*.v.me https://*.visa.com https://*.unica.com https://ad.doubleclick.net;style-src 'self' 'unsafe-inline' https://*.visa.com;object-src https://*.v.me https://*.visa.com data:;report-uri /logging/logCSPReport;
X-WebKit-CSP-Report-Only: default-src 'self' https://*.v.me https://*.visa.com;script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.visa.com https://*.v.me;img-src 'self' https://*.v.me https://*.visa.com https://*.unica.com https://ad.doubleclick.net;style-src 'self' 'unsafe-inline' https://*.visa.com;object-src https://*.v.me https://*.visa.com data:;report-uri /logging/logCSPReport;
Content-Type: application/json;charset=UTF-8
Content-Length: 130
X-Cnection: close
X-Cnection: close
Date: Fri, 19 May 2017 14:47:49 GMT
Connection: keep-alive
{"responseStatus":{"code":"9124","severity":"ERROR","info":"","status":400,"message":"Expected input credential was not present"}}
Hello,
We have reviewed the payload, you are not sending the valid creds or cert which is causing our gateway exception, Please follow the getting started guide exact steps for cert chaining and doing Mutual Auth calls.
Please let us know whats the results.
Thanks
Sanobar
Thanks for your response.
I am able to get the response using the *.p12 certs, but getting the same exception while using *.jks certs.
I followed the exact steps to create the jks certs, attaching the *.jks file for review, please advise if I am missing anything.
Keystore password - test12
private Key password - test
Hello,
Thanks for sharing your results. i am lookin into the .jks and get back to you.
Thanks
Sanobar
I am able to run the API using *.jks, I created new key store using my own CSR and it worked using SOAP UI.