Task #4135
BII-RIB: Set Check Security Answer to Non Case Sensitive
| Status: | Work Completed-End life cycle | Start date: | February 15, 2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | March 03, 2014 | |
| Assignee: | % Done: | 0% | ||
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
During checking of security answer:
- Keep original checking: Case sensitive
- If checking on case sensitive fails, then check by doing lower case+trim
During keeping of security answer:
- Put plain text in lowercase+trim before hashing and saving to DB
History
#1
Updated by Rayvandy Gabbytian over 10 years ago
- % Done changed from 0 to 100
#2
Updated by Rayvandy Gabbytian over 10 years ago
- Status changed from Development / Work In Progress to Internal Testing
- Assignee changed from Rayvandy Gabbytian to Anonymous
- % Done changed from 100 to 0
Amy, need your help to do testing of this feature.
How to test:
- Switch to branch #4135 @RIB OR merge UAT branch with branch #4135.
- login user aditya3, openam mockup=true
- change security question: test with "Default", "default", "de f a u lt ", etc
- save the changes with above pattern, and test verify again.
- reset password > verify security answer
- new user, migration user (i will test later, no data)
If it's okay, I will deploy to UAT later.
Thanks.
#3
Updated by Rayvandy Gabbytian over 10 years ago
- Status changed from Internal Testing to User Acceptance Test
- Assignee changed from Anonymous to Rayvandy Gabbytian
Already deployed to UAT on 20th February 2014
#4
Updated by Rayvandy Gabbytian over 10 years ago
- Due date changed from February 15, 2014 to March 03, 2014
- Status changed from User Acceptance Test to Work Completed-End life cycle
Deployed to production on March 3rd 2014.