Bookshelf v7.5: Editing Parameter Values in the eapps.cfg File

Provide the parameter values in the eapps.cfg file as indicated by the guidelines in Table 12.

For information about editing eapps.cfg parameters and about the purposes for the parameters, see Parameters in the eapps.cfg File.

Table 12. Parameter Values in eapps.cfg File
Section	Parameter	Suggested Entry	Guideline
[defaults]			The values of the parameters in this section are overridden by the parameter values you set in the sections for individual applications.
The section particular to your application, such as [/eservice], [/echannel], or [/callcenter]	`AnonUserName`		Enter the user ID of the seed data User record provided for the application that you implement or of the User record you create for the anonymous user. This entry also matches the sAMAccountName entry for the anonymous user record in the directory. For example, enter `GUESTCST` for Siebel eService.
	`AnonPassword`		Enter the password you created in the directory for the anonymous user.
	`SingleSignOn`	`TRUE`
	`TrustToken`		Enter `HELLO`, or a contiguous string of your choice.
	`UserSpec`	`REMOTE_USER`	REMOTE_USER is the default Web server variable in which the user's identity key is placed for retrieval by the authentication manager.
	`UserSpecSource`	`Server`	REMOTE_USER is a Web server variable.
	`ProtectedVirtualDirectory`		Generally, you would enter the name of the protected virtual directory that you created in Creating Protected Virtual Directories. For more information on usage for this parameter, see Parameters in the eapps.cfg File.
	`AnonUserPool`		If this parameter is present, comment it out with a semicolon at the beginning of the line. Alternatively, you can delete this parameter line from the file.

CAUTION: If your implementation uses a header variable to pass a user's identity key from the third-party authentication service, then it is the responsibility of your third-party or custom authentication client to set the header variable correctly. The header variable should only be set after the user is authenticated, and it should be cleared when appropriate by the authentication client. If a header variable passes an identity key to the Siebel authentication manager, and the trust token is also verified, then the user is accepted as authenticated.