Task #10754
[Internal Testing] wsCheckTokenStatus Response is not in ArrayList
Status: | Internal Testing | Start date: | April 27, 2020 | ||
---|---|---|---|---|---|
Priority: | Normal | Due date: | April 28, 2020 | ||
Assignee: | Rayvandy Gabbytian | % Done: | 80% | ||
Category: | - | Spent time: | - | ||
Target version: | - |
Description
Dear Chee Onn,
Can you check below issue:
Reported Issue:
When there are multiple token, the response only return responseCode
Expected:
To return multiple tokenSerialNo and tokenStatus as per TSD
Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.cas.penril.net"> <soapenv:Header/> <soapenv:Body> <ws:wsCheckTokenStatus> <ws:adminId>RCMS</ws:adminId> <ws:adminPassword>RCMSONL</ws:adminPassword> <!--1 or more repetitions:--> <ws:tokenSerialNo>2665984251</ws:tokenSerialNo> <ws:tokenSerialNo>2665984459</ws:tokenSerialNo> <ws:tokenSerialNo>2665984169</ws:tokenSerialNo> <ws:applicationId>200</ws:applicationId> </ws:wsCheckTokenStatus> </soapenv:Body> </soapenv:Envelope>
Response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <wsCheckTokenStatusResponse xmlns="http://ws.cas.penril.net"> <wsCheckTokenStatusReturn><![CDATA[<?xml version="1.0" encoding="UTF-8" standalone="yes"?><msg><msgHeader><responseCode>0</responseCode></msgHeader><msgBody/></msg>]]></wsCheckTokenStatusReturn> </wsCheckTokenStatusResponse> </soapenv:Body> </soapenv:Envelope>
Related issues
History
#1 Updated by Rayvandy Gabbytian over 4 years ago
- Subject changed from [Internal Testing] Unable to Create BIB User in IBAM and BIB to [Internal Testing] wsCheckTokenStatus Response is not in ArrayList
- Due date changed from April 27, 2020 to April 28, 2020
#2 Updated by Ngoh Chee Onn over 4 years ago
- Status changed from New - Begin Life Cycle to Internal Testing
- Assignee changed from Ngoh Chee Onn to Rayvandy Gabbytian
Hi Gabby,
Please refer below for the root cause and resolution.
Root Cause:
- Invalid response class mapping in rcasws.
Resolution:
- Remap back the correct class mapping in rcasws.
<msg>
<msgHeader>
<responseCode>0</responseCode>
</msgHeader>
<msgBody>
<token>
<tokenSerialNo>2665984169</tokenSerialNo>
<tokenStatus>0</tokenStatus>
</token>
<token>
<tokenSerialNo>2665984251</tokenSerialNo>
<tokenStatus>0</tokenStatus>
</token>
<token>
<tokenSerialNo>2665984459</tokenSerialNo>
<tokenStatus>0</tokenStatus>
</token>
</msgBody>
</msg>
#3 Updated by Rayvandy Gabbytian over 4 years ago
- Assignee changed from Rayvandy Gabbytian to Ngoh Chee Onn
Dear Chee Onn,
Reported Issue: For multiple token requests, if one token fails, the failed token does not show up.
Expected : For multiple token requests, if one token fails, the failed token should show up (1234567890).
Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.cas.penril.net"> <soapenv:Header/> <soapenv:Body> <ws:wsCheckTokenStatus> <ws:adminId>RCMS</ws:adminId> <ws:adminPassword>RCMSONL</ws:adminPassword> <!--1 or more repetitions:--> <ws:tokenSerialNo>2665993925</ws:tokenSerialNo> <ws:tokenSerialNo>1234567890</ws:tokenSerialNo> <ws:tokenSerialNo>2665984138</ws:tokenSerialNo> <ws:applicationId>200</ws:applicationId> </ws:wsCheckTokenStatus> </soapenv:Body> </soapenv:Envelope>
Response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <msg> <msgHeader> <responseCode>0</responseCode> </msgHeader> <msgBody> <token> <tokenSerialNo>2665984138</tokenSerialNo> <tokenStatus>20</tokenStatus> </token> <token> <tokenSerialNo>2665993925</tokenSerialNo> <tokenStatus>20</tokenStatus> </token> </msgBody> </msg>
#4 Updated by Ngoh Chee Onn over 4 years ago
- Assignee changed from Ngoh Chee Onn to Rayvandy Gabbytian
- % Done changed from 0 to 80
Hi Gabby,
Failed or invalid token will not show in response as what currently work for Prebind token. Somemore, TSD also didn't mention return any response code for invalid token. We should stick to existing code behavior to RCMS.
Thank you