Getting "Expected input credential was not present"

[smeet]

I am getting the following response on calling "fundstransferinquiry". The .jks is proper as it works fine when testing from local machine. awaiting for your earlist response.

RequestBody: {
"primaryAccountNumber" : "4761360580777760",
"retrievalReferenceNumber" : "939346466223",
"systemsTraceAuditNumber" : "883167"
}
Response status : HTTP/1.1 400 Bad Request

Response Headers:

X-SERVED-BY:l73c001
X-CORRELATION-ID:1511695571_073_87_l73c001_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:-1
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:Sun, 26 Nov 2017 11:26:11 GMT
Connection:close
Strict-Transport-Security:max-age=63072000 ; includeSubDomains

Response Body:
ResponseBody: {
"responseStatus" : {
"code" : "9124",
"severity" : "ERROR",
"info" : "",
"status" : 400,
"message" : "Expected input credential was not present"
}
}

[LakshanFernando]

Hi,

Thanks for your question.

As you have confirmed that API access had worked fine from another local machine and JKS file seems correct; this issue most probably can be due to the fact that your program/tool in the new machine is unable to read the JKS file during the SSL handshake. 

Therefore could you please check whether your program has read access and paths provided are correct to the JKS file?

Please let us know if issue still persist.

Thanks

Lakshan

[smeet]

Hi Lakshan,

As observed by debugging the application I am able to see the paths are proper and also the project is able to access the .jks

As I can see the request is generating in proper form. Any other suggestions ?

[smeet]

Please check the X-CORRELATION-ID:1511939337_536_77_l73c004_VDP_ARM for where am I going wrong. It would be a big help.

Thanks and Regards 

Smeet

[LakshanFernando]

Hi Smeet,

Could you please send us a list of available keys and certificates inside the JKS file?

You may use the following command.

keytool -list -v -keystore C:\truststore.jks

Thanks

Lakshan

[smeet]

Hi Lakshan,

Please find below details for what you asked for :-

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 2 entries

Alias name: 1
Creation date: 22 Sep, 2017
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: C=IN, ST=Maharashtra, L=Namia, O=Software Development, OU=Product Development, CN=4de6145d-0327-4965-9f0f-93b15187c7b4, UID=4de6145d-0327-4965-9f0f-93b15187c7b4, EMAILADDRESS=ngpyal@gmail.com
Issuer: C=US, O=VDPVISACA, CN=VDPCA
Serial number: 2f222c875adcd363
Valid from: Fri Sep 22 14:18:47 IST 2017 until: Sun Sep 22 14:18:47 IST 2019
Certificate fingerprints:
MD5: EF:0B:4F:D8:7B:E5:0A:18:4B:9B:8C:6E:C8:27:B1:DD
SHA1: 38:C5:D0:BD:2E:82:02:BF:A7:AB:BF:A4:11:DA:DA:FF:C8:67:FB:28
SHA256: 85:D7:24:D6:CD:2F:C9:48:82:E8:17:9C:D7:20:69:4D:5E:4D:BC:F1:45:BC:62:3A:FA:64:95:92:32:D0:CF:78
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Extensions:

#1: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: AF DD 6E B6 A0 4B 9C 79 B9 16 08 62 E6 23 31 10 ..n..K.y...b.#1.
0010: A7 82 EB A1 ....
]
]

#2: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:false
PathLen: undefined
]

#3: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
clientAuth
emailProtection
]

#4: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
DigitalSignature
Non_repudiation
Key_Encipherment
]

#5: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: E0 7B ED EE FB 91 97 A3 4B 3E FC 80 6E D6 F8 15 ........K>..n...
0010: 38 AF 28 6B 8.(k
]
]

*******************************************
*******************************************

Alias name: ejbca
Creation date: 22 Sep, 2017
Entry type: trustedCertEntry

Owner: C=US, O=VDPVISACA, CN=VDPCA
Issuer: C=US, O=VDPVISACA, CN=VDPCA
Serial number: 2d1ed295f96ad97a
Valid from: Fri Jul 24 09:57:37 IST 2015 until: Mon Jul 21 09:57:37 IST 2025
Certificate fingerprints:
MD5: 86:73:94:83:49:00:9D:82:CF:A0:BD:FE:F2:E3:95:F3
SHA1: A9:30:33:1C:EC:50:7C:71:60:51:4E:03:FF:9E:C1:CA:E6:FE:EC:C4
SHA256: 8D:65:FA:35:59:FD:C3:43:F0:E6:F0:DF:AB:03:DE:49:F3:76:14:20:22:69:C4:B2:56:1A:AC:24:07:7B:C1:F6
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Extensions:

#1: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: AF DD 6E B6 A0 4B 9C 79 B9 16 08 62 E6 23 31 10 ..n..K.y...b.#1.
0010: A7 82 EB A1 ....
]
]

#2: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:true
PathLen:2147483647
]

#3: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
DigitalSignature
Key_CertSign
Crl_Sign
]

#4: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: AF DD 6E B6 A0 4B 9C 79 B9 16 08 62 E6 23 31 10 ..n..K.y...b.#1.
0010: A7 82 EB A1 ....
]
]

*******************************************
*******************************************

[LakshanFernando · Accepted solution]

Hi Smeet,
I only can see your private key file and Visa Root Certificate file inside your JKS file.
Could you please confirm those are the only files you have added in to it?

You should add two more certificates, which are,

1. Geotrust certificate file
2. Application certificate file.

You can download them from your VDP project dashboard.
Please refer the attached screen shot as well.

Once done, please give another try and kindly update us as well.

Thanks
Lakshan