|
Application Guide for Oracle Self-Service E-Billing (Consumer Edition) > Customer Service Representative Use Cases >
Setting CSR Account Lockout Status
This use case describes the trigger points that cause Oracle Self-Service E-Billing to lock a CSR user account, preventing the user from logging in. Table 59 lists and describes the Setting CSR Account Lockout Status use case functions.
Table 59. Setting CSR Account Lockout Status
|
|
Name |
Setting CSR Account Lockout Status |
Feature Area |
Login and Authentication |
User |
CSR administrator |
Trigger |
The following conditions can trigger an account lockout:
- On the Login page a user tries logging in more than five (configurable) times.
- During the Forgot Password and Reset Password use case, when a user tries more than five (configurable) times to enter his or her User Name, Account Number, or Service Number.
- During the Forgot Password and Reset Password use case, when a user tries more than five (configurable) times to enter his or her security question or security answer.
- The user or CSR has not clicked on the HTTPS link within four hours of being sent.
|
Prerequisites |
The CSR user is currently enrolled in Oracle Self-Service E-Billing. |
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.
- Number of hours before the account locks during the HTTPS validation request.
|
Functions |
The value set in the database is unique for each trigger point. |
Main Path for Setting the Account Lockout Status
The main path for a CSR to set the account lockout status for a user is as follows:
- One of the following activities occurs, triggering an account lockout:
- A user attempts to log in.
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.
|
