|
Application Guide for Oracle Self-Service E-Billing (Consumer Edition) > Enrollment and Login Use Cases >
Setting Account Lockout Status
In this use case, various triggers cause an account to lock. The locked account prevents the user from logging in to Oracle Self-Service E-Billing. Table 8 lists and describes the Setting Account Lockout Status use case functions.
Table 8. Setting Account Lockout Status
|
|
Name |
Setting Account Lockout Status |
Functional Area |
Login and Authentication |
Primary Users |
Consumer user, CSR administrator. The CSR administrator can have super or normal privileges. |
Prerequisites |
Consumer user is currently enrolled in Oracle Self-Service E-Billing |
Trigger |
- On the Login page a user tries more than five (configurable) times to log in.
This counter is stored in the database, so time is not relevant.
- In the Forgot Password and Reset Password use case, when a user tries more than five (configurable) times to enter the user name, account number, or service number.
This is a counter that must be stored in the database, so time is not relevant.
- In the Forgot Password and Reset Password use case, when a user tries more than five (configurable) times to enter the Security Question or Security Answer.
This is a counter that must be stored in the database, so time is not relevant.
|
Configuration Points |
- Number of incorrect entries on the Login page
- Number of incorrect entries on the Forgot Password use case- Password
- Number of incorrect entries on the Forgot Password use case - Security Question
|
Functions |
- The value set in the database must be unique for each trigger point.
|
Main Path for Set Account Lockout Status
The main path to set lockout status is as follows:
- Oracle Self-Service E-Billing displays the Login page with the following error message: Please contact your customer self service representative at xxx-xxx-xxxx to get your account reactivated.
- Oracle Self-Service E-Billing sets the status flag in the database indicating this account has been locked for one of the reasons described in Table 8.
|
