Bookshelf Home | Contents | Index | PDF     

Implementation Guide for Oracle Self-Service E-Billing > Customizing User Management >

Using or Simulating Single Sign-On

You must configure Oracle Self-Service E-Billing to use an external identity store. Follow the procedure for your implementation:

Configuring Oracle Self-Service E-Billing to use a Single Sign-on System

Follow this procedure to configure Oracle Self-Service E-Billing to use a single sign-on system.

To configure Oracle Self-Service E-Billing to use a single sign-on system

  • Prepopulate the OLTP table data shown in Table 6. You do not need to populate the PASSWORD column in the EDX_BSL_AUTH_SECPROFILE table.
Table 6. User Data for Single Sign-on
Database Table
Columns to Populate
Notes

EDX_BSL_UMF_USER

ID

Required; unique for all users.

 

USERID

Required; unique for all users.

 

SECURITYPROFILEID

References the PROFILEID column in the EDX_BSL_AUTH_SECPROFILE table. Required; unique for all users.

 

COMPANYID

Required for B2B.

 

EMAIL1

Required.

 

DATE_CREATED

Required.

 

DATE_MODIFIED

Required.

 

VERSION

Required; the default is 0.

EDX_BSL_AUTH
_SECPROFILE

PROFILEID

Required; unique for all users.

 

USERID

Required; unique for all users.

 

STATUS

Required for the activity user; the default is 2.

 

PASSWORD

Required if you are simulating single-sign, or using an external identity store but using Oracle Self-Service E-Billing authentication. The password can have any value.

 

ISLOCKED

Required for the activity user; the default is 0.

 

SECURE_SUBKEY_ID

Data type is NUMBER(19,0). This column references the ID column in the EDX_SECURE_SUBKEY table. Required; the default is 1.

EDX_BSL_SEC_PROF
_ROLES_LINK

PROFILE_ID

References the PROFILEID column in the EDX_BSL_AUTH_SECPROFILE table. Required; unique for all users.

 

ROLE_ID

References the ID column in the EDX_BSL_AUTH_SECROLE table. Required.

EDX_UMF_USER_ACCT_LINK

USERID

References the USERID column in the EDX_BSL_UMF_USER table. Required for a B2C user.

 

ACCOUNT_KEY

References the NODEID in the EDX_BSL_AMF_BACCOUNT table. Required for a B2C user.

EDX_UMF_USER_ACCT_LINK (OLAP)

USERID

Required for B2C reporting.

 

ACCOUNT_KEY

References the ACCOUNT_KEY column in the edx_rpt_account_dim table. Required for B2C reporting.

Configuring Oracle Self-Service E-Billing to Simulate a Single Sign-on System

Follow this procedure to simulate a single sign-on system if you use an external identity store but use Oracle Self-Service E-Billing to authenticate users.

To configure Oracle Self-Service E-Billing to simulate a single sign-on system

  1. Populate the OLTP database with the data shown in Table 6.

    The PASSWORD column in the EDX_BSL_AUTH_SECPROFILE is required and must have an appropriate encrypted value. You can get the decrypted password from the external identity store. Use the following APIs for password encryption and to update the subkey ID in the user security profile table:

    LookupService lookUp = LookupServiceFactory.getInstance();

    ICryptography cryptography = (ICryptography) lookUp.getModule("cryptography");

    String hashPassword = cryptography.hash(plainPassword);

    ISubkeyCrypto SubkeyCrypto = EBillingServiceFactory.getSubkeyCryptoService().createSubkeyCrypto(null);

    String enPassword = SubkeyCrypto.encrypt(hashPassword);

    securityProfile.setSubkeyId(SubkeyCrypto.getSecureSubkeyID());

  2. Log in to the Billing and Payment application using the following URL and credentials (password and user name). The j_password parameter can be plain text or encrypted by the cryptography module when sending the log in request URL:

    http://ServerName:PortNum/ebilling/j_acegi_security_check?j_username=Username&j_password=Password

    where:

    • Username is the name of the user you are impersonating.
    • Password is the password of the user you are impersonating.
    
Implementation Guide for Oracle Self-Service E-Billing Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.