Support #10102
[Request ID :##5067##] : Mobile Authorisation Code - On Behalf UAT#33 Web Mobile transaction approval for verifier and releaser encounter error message
| Status: | Closed - End of life cycle | Start date: | August 09, 2019 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
Hi Stephanie.
Kindly attend below request.
From the cas.log, found that the CAS result for tokenVerifySign is shown the value as ‘97’ and causing the mobile screen hits “Invalid Authorisation Code” error upon [Verify]/[Release] action.
Thank you.
History
#1
Updated by Stephanie Sufrapto about 5 years ago
- Status changed from New - Begin Life Cycle to Development / Work In Progress
- % Done changed from 0 to 100
09 August 2019
From the log sent to us, we return success. Below log snapshot
[8/8/19 15:19:52:384 MYT] 00000049 ServiceManage I Invoke WS-API verifySimpleLogin with NONCE
[8/8/19 15:19:52:386 MYT] 00000049 ServiceManage I userId=MYCH002
[8/8/19 15:19:52:388 MYT] 00000049 ServiceManage I companyId=MYCHARLIE
[8/8/19 15:19:52:390 MYT] 00000049 ServiceManage I applicationId=200
[8/8/19 15:20:17:823 MYT] 00000049 Authenticatio I TokenManagementServiceImpl.verifyTokenOTP() - verifyOTP1 - START 8b54a190-c766-43a3-99ae-66ac6fdc696c
[8/8/19 15:20:17:830 MYT] 00000049 TokenManager I Return Code = 0
[8/8/19 15:20:17:832 MYT] 00000049 TokenManager I Token verification success!
[8/8/19 15:20:17:834 MYT] 00000049 Authenticatio I TokenManagementServiceImpl.verifyTokenOTP() - verifyOTP1 - END 8b54a190-c766-43a3-99ae-66ac6fdc696c [Time taken:11 ms]
[8/8/19 15:20:17:836 MYT] 00000049 Authenticatio I Response Code = 0
[8/8/19 15:20:17:838 MYT] 00000049 Authenticatio I TokenManagementServiceImpl.verifyTokenOTP() - updateTokenSuccess - START 8b54a190-c766-43a3-99ae-66ac6fdc696c
[8/8/19 15:20:17:850 MYT] 00000049 Authenticatio I TokenManagementServiceImpl.verifyTokenOTP() - updateTokenSuccess - END 8b54a190-c766-43a3-99ae-66ac6fdc696c [Time taken:12 ms]
[8/8/19 15:20:17:852 MYT] 00000049 Authenticatio I TokenManagementServiceImpl.verifyTokenOTP() - END 8b54a190-c766-43a3-99ae-66ac6fdc696c [Time taken:61 ms]
[8/8/19 15:20:17:885 MYT] 00000049 BaseServices I Response for wsVerifyTokenOTP : 85aa96bb-a679-4242-a083-f9e562d524dd <msg><msgHeader><responseCode>0</responseCode></msgHeader><msgBody/></msg>
[8/8/19 15:20:17:888 MYT] 00000049 BaseServices I CASServices.wsVerifyTokenOTP() - END 85aa96bb-a679-4242-a083-f9e562d524dd [Time taken:137 ms]
Asking RCAS to clarify more regarding this? Is issue happened in UAT?
s user accessing RCMS from Mobile web browser or mobile apps?
#2
Updated by Stephanie Sufrapto about 5 years ago
- Status changed from Development / Work In Progress to Pending Customer Feedback
- Assignee changed from Stephanie Sufrapto to Zahir Abd Latif
No Feedback from customer.
Please close this issue
#3
Updated by Zahir Abd Latif about 5 years ago
- Status changed from Pending Customer Feedback to Closed - End of life cycle
Issue closed in SCP.