Support #13544
[SCP ID :##6708##] : (97) REST CUA ERROR: FAILED TO REGISTER DEVICES : SYAFAFWATI BINTI ABU HASHIM : MY0908662
| Status: | Work Completed-End life cycle | Start date: | June 22, 2023 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | RIB | Spent time: | - | |
| Target version: | - |
Description
Hi Balqis,
Kindly attend below request.
Customer called CC inquiry on Agrokey activation for RIB acc. Agent already guides customer several times but still unable to activate Agrokey. Once customer complete to fill in the details, system appear error “97 (REST CUA ERROR)”. Name : SYAFAFWATI BINTI ABU HASHIM NRIC : 840922086448 Mobile number : 0103933209 Username : atie2209 Device : Vivo 2020, android 11 Timestamp : 17/06/2023 4.30 pm Log 14 – 18 can be found here \\172.16.49.7\prod logs\VPIBKU01\19062023 \\172.16.49.7\prod logs\VPIBKU02\19062023
Thank you.
History
#1
Updated by Siti Balqis Othman about 1 year ago
- Status changed from New - Begin Life Cycle to System Integration Test
- % Done changed from 0 to 100
Finding:
After investigating the request data sent by Mobile Banking to perform the mobile token activation process. We notice there is a special symbol/ special character in the device info value as per request body below.
This has caused the API to have problems communicating with UPASS RESTFUL when it finds a special symbol in the Device Info data. This is because the API considers it as part of the UPASS-RESTFUL URL.
INFO ] 2023-06-17 16:29:14.792 [WebContainer : 21] RestSecureOTPServices - {
"headerRequest" : {
"locale" : "en",
"remoteIpAddress" : "172.16.51.53",
"appId" : "UpassAdminRIB",
"appKey" : "xxxxxx",
"channelId" : "2",
"sessionId" : "2023061716252555166947",
"hashMsg" : "xxxxx",
"version" : ""
},
"bodyRequest" : {
"userName" : "xxxxxxx",
"regCode" : "28714301",
"fcmToken" : "xxxxxx",
"deviceInfo" : "DeviceName:$*¥*F@Fw@T!|Model:V2043|OSType:A|OSVersion:30",
"tacNo" : "222012",
"id" : "6448"
},
"footerRequest" : { }
Solution:
Encode the device info for handling special characters in HTTP requests. Then, decode it after success reaches UPASS-RESTFUL to perform mobile token activation.
The patch already deployed to SIT for ITD to perform testing
#2
Updated by Siti Balqis Othman about 1 year ago
- Status changed from System Integration Test to Work Completed-End life cycle
- Assignee changed from Siti Balqis Othman to Zahir Abd Latif
Migrated to production on 04/08/2023 under Migration ID209