Customer Portal - User Activation

Get Started. It's Free
or sign up with your email address
Rocket clouds
Customer Portal - User Activation by Mind Map: Customer Portal - User Activation

1. validations

1.1. all fields invalid

1.2. username empty and passwords match but less than 8 chars

1.3. all fields empty

1.3.1. proper error message as per deisgn

1.4. username empty and passwords does not match but more than 8 chars

1.5. username empty and passwords does not match and less than 8 chars

1.6. username used previously in the system

1.7. Username

1.7.1. does not accept more than maximum

1.7.2. accepts special characters??

1.7.2.1. we need to research

1.7.3. cannot be duplicated in the system

1.7.3.1. what will be the error message

1.8. Password

1.8.1. does not accept more than maximum

1.8.2. accepts special characters??

1.8.2.1. p`[email protected]#o$r%d^&*()_-+='";:,.<>123

1.8.3. does not accept less than 8 chars

1.8.4. stored salted and hashed

1.9. confirm password

1.9.1. does not accept more than maximum

1.9.2. accepts special characters??

1.9.3. does not accept less than 8 chars

2. UI

2.1. Activation email

2.1.1. as per design

2.1.1.1. IPB-20762

2.2. Link expired screen or used previously

2.2.1. as per design

2.3. Contact US modal

2.3.1. as per design

2.4. Register Page

2.4.1. as per design including error messages

2.4.1.1. IPB-20763

2.4.2. tabs are working properly

2.4.3. enter is triggering submit action

2.4.4. Password masking

2.4.4.1. create password

2.4.4.1.1. password is masked by default

2.4.4.1.2. user will see the last digit even while the password is masked ?

2.4.4.1.3. user can unmask the password before starting to write? will he write the password now in clear text?

2.4.4.1.4. typing after unmasking will automatically mask the password?

2.4.4.1.5. user can mask the password after unmasking

2.4.4.1.6. user types few letters them unmask then mask then continue typing

2.4.4.2. Confirm create password

2.4.4.2.1. password is masked by default

2.4.4.2.2. user can mask the password after unmasking

2.4.4.2.3. user types few letters them unmask then mask then continue typing

2.5. Welcome email

2.5.1. as per design

2.5.1.1. IPB-20765

2.6. Landing page

2.6.1. T & C

2.6.2. as per design

2.7. Password Strength

2.7.1. password less than 8 chars

2.7.1.1. meter 1 dash and color red

2.7.1.2. popup on mouse over?? "Your password must be at least 8 chars"

2.7.1.3. popup displayed automatically on stop typing or leaving? "Your password must be at least 8 chars"??

2.7.2. 8 chars or more but weak

2.7.2.1. meter 1 dash and color red

2.7.2.2. popup on mouse over?? "Please make sure you password is not common...."

2.7.2.3. popup displayed automatically when password is calculated "Please make sure you password is not common...."

2.7.3. Good strength

2.7.3.1. meter has 2 green dashes

2.7.3.2. text should be "your password is good....."

2.7.3.3. on mouse over or password calculation ??

2.7.4. Strong password

2.7.4.1. meter has 3 green dashes

2.7.4.2. text should be "Your password is excellent..."

2.7.4.3. on mouse over or password calculation ??

2.7.5. by default meter is displayed in grey

2.7.6. as per design

3. Functionality

3.1. Customer Registration

3.1.1. Customer First registration

3.1.1.1. customer click on registration link after 48 hours

3.1.1.1.1. code expires after 48 hours

3.1.1.1.2. proper screen is displayed

3.1.1.1.3. link for signup page to be displayed in the expiry message

3.1.1.2. Customer clicks on link after 47 hours

3.1.1.2.1. code does not expire

3.1.1.2.2. username creation screen is displayed

3.1.1.3. Customer tries to register twice with the same link

3.1.1.3.1. code can be used only once

3.1.1.3.2. proper screen to be displayed that this link was used previously

3.1.1.4. Successful Registration

3.1.1.4.1. Landing page is displayed with terms and conditions

3.1.1.4.2. username and password are saved in db

3.1.1.4.3. password is sanitized in db

3.1.1.4.4. user status changed from inactive to active

3.1.1.4.5. welcome email is received and should be as per design

3.1.1.4.6. if user has multiple emails and no one preferred , the used email during registration will be marked preferred in ELK

3.1.2. Customer not activated and tries to register again

3.1.2.1. previous link did not expire

3.1.2.1.1. new activation code is created and send to the preferred email

3.1.2.1.2. use old activation code

3.1.2.1.3. use new activation code

3.1.2.2. previous link expired

3.1.2.2.1. new activation code is created and send to the preferred email

3.1.2.2.2. use new activation code

3.1.2.2.3. user cannot use old expired code to activate

3.2. Email Resend

3.2.1. user did not change the email

3.2.1.1. token expired

3.2.1.1.1. new token created in database

3.2.1.1.2. the new token received properly in the email

3.2.1.2. token did not expire

3.2.1.2.1. no new token created in db

3.2.1.2.2. the old token is sent in a new email

3.2.2. user changed the email

3.2.2.1. email should be sent to the email related to the current code

3.2.3. "email has been sent" should be displayed when user click resend

3.2.3.1. IPB-20382

3.3. Strength Meter

3.3.1. strength is calculated properly

3.3.1.1. Points are calculated as per requirement

3.3.1.1.1. Score the input/password out of 10. Start at 0 for passwords less than 8 characters; +2 for 8 and more characters in the password When 8-characters password is reached, add: +0 if the password has appeared in a breach equal or more than 100 times. +2 if the password has appeared in a breach between 99 & 50. +4 if the password has appeared in a breach between 1 & 49. +6 if the password has not appeared.

3.3.1.1.2. try to test boundries 49,50,99,100

3.3.1.2. strength is calculated as per the points

3.3.1.2.1. Weak = 0-3 points

3.3.1.2.2. Good =4-6 points

3.3.1.2.3. Excellent =7-10 points

3.3.1.2.4. test the boundaries 3,4,6,7

3.3.2. Log

3.3.2.1. log is created once username and password are generated

3.3.2.2. log is anonymous

3.3.2.3. log saves password strength, number of breaches and timestamp

3.3.3. calculation event

3.3.3.1. calculated on leave password

3.3.3.2. on stop typing for 3 seconds

3.3.3.3. if user continues types after calculation new calculation happens