Application Guide for Oracle Self-Service E-Billing (Consumer Edition) > Enrollment and Login Use Cases >

Logging In


In this use case, a user logs in to the Web site to access Oracle Self-Service E-Billing. Table 8 lists and describes the use case functions.

Table 8. Logging In
Functions
Description

Name

Logging In

Functional Area

User Management

Primary Users

Consumer user

Trigger

The user navigates to the Login page by entering the URL into a supported browser or user follows a link from service provider's landing page available to all anonymous users.

Standard Features

  • Validation of the username and password input.
  • Authentication of the user name and password.
  • Change Language action.
  • Enroll as a new user link.
  • Disclaimer text and standard footer links.

Configuration Points

  • Validation rules for username and password.
    • Username: (Default) The user's telephone number alternative is first initial and full last name (non-phone user login).
    • Password: (Default) Must be at least six characters and must contain at least one uppercase letter, one lowercase letter, and one number to comply with Sarbanes-Oxley guidelines.
  • Ability to force users to change their passwords at first login if the username and password were created by a CSR or a company administrator.
  • Change Language: The default is U.S. English, however all Unicode scripts and languages are configurable.
  • Parameters can be passed through the URL with a secure token that contains the preferred language, currency, and market segment information to personalize the user's experience. For example, if a user has changed the language preference on the service provider's consumer portal page, the Login screen must be presented in the same language, if available, and set for the remainder of the user's session until changed by the user.
  • Ability to bypass the Login screen to use single sign-on (SSO) applications (for example, Siebel CRM, Oracle Identity Manager, CA SiteMinder or other third-party application). Along with the Login information, the user's language and currency preference can be passed to Oracle Self-Service E-Billing to set user preferences.

Main Path for Logging In

The following path describes user login:

  1. The user enters login information:
    • Username
    • Password
  2. The user clicks Submit.
  3. Oracle Self-Service E-Billing validates data and identifies the user's data access and permissions:
    • Vertical: Telco is the default
    • Market: Consumer
    • Role: Determines permissions
    • Access: Data access
  4. Oracle Self-Service E-Billing displays the default page determined by the user's attributes (Vertical, Market, Role, Method, Access, and Language).

Alternate Paths for Logging In

Alternate paths can occur in this use case.

The customer's login credentials are invalid.

The UI displays the message: The sign-in information you have entered does not match what we have on file, Please reenter your sign-in information.

The user clicks the change language link.

The UI provides a screen to select alternate language for the display of the Login screen and sets the selected language preference for the duration of the user's session or until changed by the user.

The user clicks the Enroll tab.

The UI displays the Enrollment use case.

Application Guide for Oracle Self-Service E-Billing (Consumer Edition) Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.