Siebel Installation Guide for UNIX > Requirements for Installing and Configuring Siebel Business Applications > Requirements for Installing and Configuring the Siebel Web Server Extension >

Requirements for Configuring Anonymous Users for the Siebel Web Server Extension

As noted in Configuring the SWSE Logical Profile, when you configure the SWSE logical profile, you are prompted for user names and passwords of Siebel users who will serve as anonymous users for employee applications and customer applications, respectively. Provide the anonymous user credentials, as appropriate for your deployment. Strong passwords are highly recommended for anonymous user accounts.

This topic is part of Requirements for Installing and Configuring the Siebel Web Server Extension.

The following are the two main types of anonymous users:

• Anonymous user for employee applications. The anonymous user for employee applications (sometimes called the employee user or the high interactivity user) starts the anonymous session that displays the login page to an end user for an employee application. (Employee applications can be deployed using either high interactivity or Siebel Open UI.)
• Anonymous user for customer applications. The anonymous user for customer applications (sometimes called the contact user or the standard interactivity user) starts the anonymous session that displays the login page to an end user for a customer application, and allows anonymous navigation within the application. This user must have access to any public view in the application.

If, after initial configuration, you change the password for the database account that you are using for an anonymous user, or decide to specify a different anonymous user for a particular application, then you can edit the eapps.cfg or eapps_sia.cfg files manually to specify the necessary data. Alternatively, you can re-create the SWSE logical profile and reapply it to each physical SWSE.

To manually edit the eapps.cfg and eapps_sia.cfg files after configuration to update anonymous user settings, you update values for the parameters AnonUserName and AnonPassword.

Record the credentials for each anonymous user in your deployment in the worksheet provided in Siebel Deployment Planning Worksheet.

For additional information about configuring anonymous users, see Siebel Security Guide.

Note the following guidelines and requirements:

• All anonymous users for your deployment must be defined in the Siebel database and must be defined as Siebel users. Anonymous users should have limited access rights, no more than is necessary for the usage context.
• If password encryption is in effect, then you must use the encryptstring utility to encrypt any password before inserting it into eapps.cfg or eapps_sia.cfg as a value for AnonPassword. See also 475381.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Alert 1306.
• The anonymous user for employee applications that you configure in the wizard is defined in eapps.cfg as a default that applies to all of the applications of this type. The AnonUserName and AnonPassword parameters are defined once, in the [defaults] section of this file.
• The anonymous user for customer applications that you configure in the wizard is defined in eapps.cfg and eapps_sia.cfg for each application of this type. The AnonUserName and AnonPassword parameters are defined in separate application-specific sections of these files.
• To use application-specific anonymous users, you must define AnonUserName and AnonPassword in separate application-specific sections of eapps.cfg and eapps_sia.cfg. Example applications include Siebel Partner Relationship Management (PRM) and Siebel Employee Relationship Management (ERM).
• Optionally, you can create new database users before initial configuration through editing the grantusr.sql script, which you review, modify, and execute before you install the Siebel database. You still must add corresponding Siebel users. For more information, see Creating Table Owner and Administrator Accounts.