Closed ArjunLokanath closed 7 years ago
May from APAC Venture had mentioned that this needs to be checked by the ABL team
Currently system parameter is set to 5 times. Can try if failed to login for 5 times?
Hi Jason,
The test conducted is as per the details mentioned in the Functional Specs, Hence it will still be considered as a defect if the FS has not been updated accordingly (5 times), Thanks
Best Regards, Arjun Lokanath Test Manager, AppSync Malaysia HP: 01135443870
On Tue, Nov 15, 2016 at 11:38 AM, JasonABL notifications@github.com wrote:
Currently system parameter is set to 5 times. Can try if failed to login for 5 times?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/56#issuecomment-260538702, or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_lHWrvAlFBbSjlyryTJSO6d0qQEqks5q-SkYgaJpZM4KyEtD .
This is indeed a problem with the backend. Will update again once mitigate the problem.
abl changed parameter from 5 to 3.
abl to return proper response code to apac.
apac to alert user by giving pop up (similar like pin)
Thanks Raymond and any update on this fix? Thanks
Best Regards, Arjun Lokanath Test Manager, AppSync Malaysia HP: 01135443870
On Tue, Nov 15, 2016 at 6:52 PM, raymondabl notifications@github.com wrote:
This is indeed a problem with the backend. Will update again once mitigate the problem.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/56#issuecomment-260610287, or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_p0FHBsXplFwA4jgCGOT_b4ADgkBks5q-Y74gaJpZM4KyEtD .
Hi,
Bug have fixed, please retry for testing.
Regards, Jason
Hi Jason,
Just tested on the Android version now and after 3 incorrect passwords the error message: "Invalid Customer" is being displayed however the expectation is that the User knows he/ she is being locked out due to 3 consecutive invalid attempts and User have to call the Customer service to unblock so kindly help to correct this, Thanks
Best Regards, Arjun Lokanath Test Manager, AppSync Malaysia HP: 01135443870
On Mon, Nov 21, 2016 at 5:01 PM, JasonABL notifications@github.com wrote:
Hi,
Bug have fixed, please retry for testing.
Regards, Jason
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/56#issuecomment-261881051, or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_m_EB9swHEF6ChxZb2szeA69q29Dks5rAV36gaJpZM4KyEtD .
Adding on, It was also noted that the User Account was locked out after 3 times on iOS whereas it locked out after 6 times on Android version.. Thanks
Best Regards, Arjun Lokanath Test Manager, AppSync Malaysia HP: 01135443870
On Mon, Nov 21, 2016 at 5:13 PM, Arjun Lokanath arjun.lokanath@appsync.sg wrote:
Hi Jason,
Just tested on the Android version now and after 3 incorrect passwords the error message: "Invalid Customer" is being displayed however the expectation is that the User knows he/ she is being locked out due to 3 consecutive invalid attempts and User have to call the Customer service to unblock so kindly help to correct this, Thanks
Best Regards, Arjun Lokanath Test Manager, AppSync Malaysia HP: 01135443870
On Mon, Nov 21, 2016 at 5:01 PM, JasonABL notifications@github.com wrote:
Hi,
Bug have fixed, please retry for testing.
Regards, Jason
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/56#issuecomment-261881051, or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_m_EB9swHEF6ChxZb2szeA69q29Dks5rAV36gaJpZM4KyEtD .
Hi Arjun,
I’m not sure why this happening, API are standards. It’s not possible having different counts of failed attempts for IOS and Android.
Please check with Apac.
Regards,
Jason
From: Arjun Lokanath [mailto:arjun.lokanath@appsync.sg] Sent: Monday, 21 November 2016 5:19 PM To: TNGSB/eWallet reply@reply.github.com; Jason Pang jason@ablglobal.com Cc: TNGSB/eWallet eWallet@noreply.github.com; Author author@noreply.github.com; Bavani Shanmugam bavani@touchngo.com.my; Farah Ain Mohamad farah.mohamad@appsync.sg Subject: Re: [TNGSB/eWallet] eWallet_MobileApp_The User Account is not being locked out even after 3 failed attempts to login # 56 (#56)
Adding on, It was also noted that the User Account was locked out after 3 times on iOS whereas it locked out after 6 times on Android version.. Thanks
Best Regards,
Arjun Lokanath
Test Manager, AppSync
Malaysia HP: 01135443870
On Mon, Nov 21, 2016 at 5:13 PM, Arjun Lokanath <arjun.lokanath@appsync.sg mailto:arjun.lokanath@appsync.sg > wrote:
Hi Jason,
Just tested on the Android version now and after 3 incorrect passwords the error message: "Invalid Customer" is being displayed however the expectation is that the User knows he/ she is being locked out due to 3 consecutive invalid attempts and User have to call the Customer service to unblock so kindly help to correct this, Thanks
Best Regards,
Arjun Lokanath
Test Manager, AppSync
Malaysia HP: 01135443870
On Mon, Nov 21, 2016 at 5:01 PM, JasonABL <notifications@github.com mailto:notifications@github.com > wrote:
Hi,
Bug have fixed, please retry for testing.
Regards, Jason
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/56#issuecomment-261881051 , or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_m_EB9swHEF6ChxZb2szeA69q29Dks5rAV36gaJpZM4KyEtD . https://github.com/notifications/beacon/AWCs_kFcJG5t1BEuSkPySaipFGWGx6Laks5rAV36gaJpZM4KyEtD.gif
Hi May,
Please advise on the below issue that has not been resolved fully, Thanks
Best Regards, Arjun Lokanath Test Manager, AppSync Malaysia HP: 01135443870
On Mon, Nov 21, 2016 at 6:19 PM, Jason Pang jason@ablglobal.com wrote:
Hi Arjun,
I’m not sure why this happening, API are standards. It’s not possible having different counts of failed attempts for IOS and Android.
Please check with Apac.
Regards,
Jason
From: Arjun Lokanath [mailto:arjun.lokanath@appsync.sg] Sent: Monday, 21 November 2016 5:19 PM To: TNGSB/eWallet <reply+0160acfe1b05d3b4b2f5941a62cc06 2b0f36f3ab52c50c2792cf00000001144a79fa92a169ce0b484be3@reply.github.com>; Jason Pang jason@ablglobal.com Cc: TNGSB/eWallet eWallet@noreply.github.com; Author < author@noreply.github.com>; Bavani Shanmugam bavani@touchngo.com.my; Farah Ain Mohamad farah.mohamad@appsync.sg Subject: Re: [TNGSB/eWallet] eWallet_MobileApp_The User Account is not being locked out even after 3 failed attempts to login # 56 (#56)
Adding on, It was also noted that the User Account was locked out after 3 times on iOS whereas it locked out after 6 times on Android version.. Thanks
Best Regards,
Arjun Lokanath
Test Manager, AppSync
Malaysia HP: 01135443870
On Mon, Nov 21, 2016 at 5:13 PM, Arjun Lokanath arjun.lokanath@appsync.sg wrote:
Hi Jason,
Just tested on the Android version now and after 3 incorrect passwords the error message: "Invalid Customer" is being displayed however the expectation is that the User knows he/ she is being locked out due to 3 consecutive invalid attempts and User have to call the Customer service to unblock so kindly help to correct this, Thanks
Best Regards,
Arjun Lokanath
Test Manager, AppSync
Malaysia HP: 01135443870
On Mon, Nov 21, 2016 at 5:01 PM, JasonABL notifications@github.com wrote:
Hi,
Bug have fixed, please retry for testing.
Regards, Jason
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/56#issuecomment-261881051, or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_m_EB9swHEF6ChxZb2szeA69q29Dks5rAV36gaJpZM4KyEtD .
<Farah 7.12.16> retest at Live, still not OK. Defect reopened
@JasonABL as discussed pls relook into the issue; still happening at Dev
fixed, kindly retry.
retested OK, closing defect
The second Business Rule stated under UC5 states that the User Account would be locked out after 3 failed attempts to login, however even after 5 failed attempts the User is still allowed to login after entering the correct password