[ASTPPCOM-844] CLONE - Setting- Global- password strength - "strong" > during change password in customer login, It accepting any weak password in customer login. Created: 19/Nov/21  Updated: 01/Mar/22  Resolved: 01/Mar/22

Status: Closed
Project: ASTPP Community
Component/s: None
Affects Version/s: v5.0
Fix Version/s: v5.0

Type: Bug Priority: Highest
Reporter: Prashant Kumar Assignee: Jaimin Solanki (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 3h
Original Estimate: Not Specified

Attachments: File eCugjhahxa.mp4     File MhinHWwkIG.mp4    
Issue Links:
Cloners
Reproducibility: always
Category: Functional
Edition: Community

 Description   

Steps to reproduce :

  1. Login as admin
  2. Go to configuration menu > Setting 
  3. Password strength is strong 
  4. Go to account > Customer 
  5. Click on create button
  6. Fill up details and save
  7. Login as customer
  8. Go to my account > Change password 
  9. Fill up old password = Test@123, new password = 12, confirm password = 12
  10. Click on submit.

Actual result :- Verify password changed successfully without any password strength  "strong" validation. 

Expected result :- password strength  "strong" should be working fine.

It should not be accept weak password.

It should be validate according to password's length, some special, lower/Upper character, numeric character etc. If password not match according to password strength  "strong" validation then it should be display error message according to mention above conditions.

See Latest  Videos.

Note:- This issues are also occurred in community v5.0 version. 

 



 Comments   
Comment by Jaimin Solanki (Inactive) [ 24/Nov/21 ]

This issue Resolved,

PR

https://github.com/iNextrix/ASTPP/pull/637

Comment by George P [ 16/Dec/21 ]

This issue is also happening to enterpise edition 5.0.

How can i update it to fix the problem?

Comment by Palak Rami (Inactive) [ 17/Jan/22 ]

Hello George P,

Its now resolved for you.

Thanks,

Palak.

Comment by Prashant Kumar [ 01/Mar/22 ]

Verified in latest source v5.0, change applied done, working fine as expected.

Generated at Sat Feb 10 07:20:46 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.