|
Application Guide for Oracle Self-Service E-Billing (Business Edition) > Enrolling and Managing Users >
Setting Account Lockout Status
In this use case, various triggers cause an account to lock and prevent the user from logging in to Oracle Self-Service E-Billing. Table 14 lists and describes the Set Account Lockout Status use case functions.
Table 14. Setting Account Lockout Status
|
|
Name |
Setting Account Lockout Status |
Functional Area |
Login and Authentication |
Primary Users |
End user, CSR administrator (Super or Normal Privileges) |
Preconditions |
The user is currently enrolled in Oracle Self-Service E-Billing. |
Trigger |
- On the Login page a user tries more then five (configurable) times to log in to the application.
This counter is stored in the database, so time is not relevant.
- In the Resetting a Password use case, when a user tries more than five (configurable) times to enter his or her 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 Resetting a Password use case, when a user tries more than five (configurable) times to enter his or her security answer or security answer.
This counter is 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 Resetting a Password flow - Password
- Number of incorrect entries on the Resetting a Password flow - Security Question
|
Notes |
The value set in the database must be unique for each trigger point. |
Main Path for Setting Account Lockout Status
The following path describes the Set Account Lockout Status use case:
- 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 14.
|
