Security Guide for Siebel eBusiness Applications > Addendum for Siebel Financial Services >

User Authentication for Siebel Financial Services

This section contains information for Siebel Financial Services applications that differs from information in other sections of this guide, or that otherwise warrants mention.

LDAP and ADSI Security Adapter Authentication

Security adapter authentication is a prerequisite if you want to implement self-registration or external administration of users. However, not all Siebel applications provide self-registration and external administration of users as default functionalities.

For information about the applications in this group that provide self-registration and external administration of users as default functionalities, see Registering and Administering Users for Siebel Financial Services.

Implementing LDAP and ADSI Security Adapter Authentication

Implementation of LDAP/ADSI security adapter authentication is the same for Siebel Financial Services applications as described in other sections of this guide, with the following exceptions.

Parameters for Siebel Financial Services applications are listed primarily in the eapps_fins.cfg file. The eapps.cfg file is also included, as documented in other sections of this guide. The eapps.cfg file has an include line that points to the eapps_fins.cfg file. References throughout this section to the eapps.cfg file should be replaced by references to the eapps.cfg file and the eapps_fins.cfg file.

Setting Up Security Adapter Authentication: A Scenario

The Responsibility and New Responsibility that are assigned to the seed anonymous user GUESTCST are intended for use with Siebel Financial Services customer applications. These responsibilities differ from the responsibilities assigned to GUESTCST for Siebel customer applications that are not specific to financial services, as documented in other sections of this guide.

If you deploy either Siebel Events Manager for Finance or Siebel customer applications that are not specific to financial services concurrently with any other Siebel Financial Services customer applications, then you must create a separate anonymous user.

The new anonymous user is used for Siebel Events Manager for Finance and for the Siebel customer applications that are not specific to financial services; that is, the applications documented in other sections of this guide. Assign this anonymous user the responsibilities as they are documented for GUESTCST in Seed Data.

When you add TESTUSER to the database, you should enter the Responsibility and New Responsibility fields with an appropriate responsibility for a typical registered user for the application you are setting up. For information about the seed responsibilities provided for specific applications, see Seed Data for Siebel Financial Services and Seed Data.

Implementing Web SSO Authentication

Implementation of Web SSO authentication is the same for Siebel Financial Services applications as described in other sections of this guide with the following exceptions.

Parameters for Siebel Financial Services applications are listed primarily in the eapps_fins.cfg file. The eapps.cfg file is also included, as documented in other sections of this guide. The eapps.cfg file has an include line that points to the eapps_fins.cfg file. References throughout this section to the eapps.cfg file should be replaced by references to the eapps.cfg file and the eapps_fins.cfg file.

Setting Up Web SSO: A Scenario

The Responsibility and New Responsibility that are assigned to the seed anonymous user GUESTCST are intended for use with Siebel Financial Services customer applications. These responsibilities differ from the responsibilities assigned to GUESTCST for Siebel customer applications that are not specific to financial services, as documented in other sections of this guide.

If you deploy either Siebel Events Manager for Finance or Siebel customer applications that are not specific to financial services concurrently with any other Siebel Financial Services customer applications, then you must create a separate anonymous user.

The new anonymous user is used for Siebel Events Manager for Finance and for the Siebel customer applications that are not specific to financial services; that is, the applications documented in other sections of this guide. Assign this anonymous user the responsibilities as they are documented for GUESTCST in Seed Data.

When you add TESTUSER to the database, you should enter the Responsibility and New Responsibility fields with an appropriate responsibility for a typical registered user for the application you are setting up. For information about the seed responsibilities provided for specific applications, see Seed Data for Siebel Financial Services and Seed Data.

Parameters in the eapps.cfg and eapps_fins.cfg Files

In addition to the eapps.cfg file, the Siebel Web Engine also uses the eapps_fins.cfg file to control interactions between Siebel Financial Services applications and the Siebel Web Engine. The section defining the Application Object Manager (AOM) and authentication parameters for an application appears once, in either the eapps.cfg file or in the eapps_fins.cfg file.

Table 30 lists the sections in the eapps.cfg file and in the eapps_fins.cfg file, which are provided for Siebel Financial Services applications.

Siebel Application Configuration File Parameters

For names of application configuration files for specific applications, see Configuration File Names for Siebel Financial Services Applications.