-
Type:
Story
-
Status: Closed
-
Priority:
Major
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: 7.3.10 DXP GA1
-
Component/s: Application Security > Multi-Factor Authentication
-
Epic Link:
-
Sprint:Iteration 30, Iteration 31, Iteration 32, Iteration 33, Iteration 34, Iteration 35, Iteration 36
-
Git Pull Request:
Description
In the first iteration of MFA implementation (MVP) this Story is used for pushing the existing code into master. In this iteration we implement the followings:
- Using primary email address - no need user level settings
- Note: in the final version, the End Users will be able to set the email address which they want to use.
- When MFA is enabled at portal instance level
- Has own UI screen
Design Deliverables
Acceptance Criteria
- As an End User, I want to be able to request a verifier code through email at appropriate step's screen using a button which code I can use during the login process at appropriate step's screen through email.
- As an End User, I want to be able to get verifier code that I can use during the login process at appropriate step's screen through email.
- As an End User, I want to use the verifier code that I got through email at appropriate step's screen through email.
- fixes
-
LPS-102017 [Backend] Reorganize existing API for the current scope
-
- Closed
-
-
LPS-102476 [Backend] Throttle Email One Time Password (OTP) verification step to prevent brute-force attack
-
- Closed
-
-
LPS-102477 [Backend] Throttle email sending at Email One Time Password (OTP) verification step to prevent brute-force attack
-
- Closed
-
- is related to
-
LPS-102021 Implement MFA Email OTP
-
- Closed
-
- relates
-
LRDOCS-7697 User Document for Multi-factor atuthentication
-
- Closed
-