Siebel Security Guide > Changing or Adding Passwords >
Changing the Siebel Enterprise Security Token
The Siebel Enterprise security token is a value that you specify when you create a Siebel Web Server Extension (SWSE) logical profile. This token serves as a password that authenticates the following:
- A Siebel administrator refreshing application images (and other static content) from the Siebel Server to the Web server without requiring a restart of the Web server.
- Requests from Siebel Management Agents during their installation.
After you apply the SWSE logical profile, the parameter SiebEntSecToken in the application sections of the eapps.cfg file stores the value you specified for the Siebel Enterprise security token. The SiebEntSecToken parameter stores the value in encrypted form if password encryption for the eapps.cfg file is in effect (EncryptedPassword = TRUE). If you manually edit the eapps.cfg file, then you must use the encryptstring utility to generate an encrypted version of the new password to store in the file. Enter the output from the encryptstring utility.
If EncryptedPassword = FALSE, passwords are not stored as encrypted values. In this case, passwords must not be entered as encrypted values.
For more information about password encryption for the eapps.cfg file, and about the encryptstring utility, see Managing Encrypted Passwords in the eapps.cfg File.
NOTE: The SiebEntSecToken parameter provides Web server security, but does not correspond to a database account and is stored only in the eapps.cfg file.
For more information about managing Web images and other files for your Siebel Business Applications, see Configuring Siebel Business Applications.
To edit the eapps.cfg file to configure the Siebel Enterprise security token
- The Web public root directory (the location of Web file caching for Siebel Business Applications) is set automatically when you apply the SWSE logical profile by running the Siebel Configuration Wizard for SWSE. Or, you can specify it by adding a line in each application section of the eapps.cfg file. For example, to specify the Web public root directory for Siebel eService (for a Web server on a Windows computer), add a parameter like this:
WebPublicRootDir = SWEAPP_ROOT\public\LANGUAGE
SWEAPP_ROOT is the SWSE installation directory, such as
LANGUAGE is the application language, such as ENU for U.S. English. Files will be copied to this location from all of the language-specific subdirectories of the directory
SIEBSRVR_ROOT is the Siebel Server installation directory.
The directory structure on the Web server is parallel to that on the Siebel Server, except that the files are moved up from their original language-specific subdirectories. For example, files would be copied from
It is recommended to set
WebPublicRootDir the same for all applications for a given language, in order to conserve disk resources on the Web server.
- The Siebel Enterprise security token can be set by applying a SWSE logical profile using the Siebel Configuration Wizard for SWSE. Or, you can specify it by adding a line in each application section of the eapps.cfg file. For example, to specify a Siebel Enterprise token for Siebel eService, add a parameter like this:
SiebEntSecToken = abcdef
Typically, password encryption is in effect for the eapps.cfg file, as described in Managing Encrypted Passwords in the eapps.cfg File. If encryption is in effect and if you edit the file manually, then you must use the encryptstring utility to generate an encrypted version of the new password to store in the file.
Siebel administrators can then use this password to update cached static files from a browser, without restarting the Web server. For example, specify a URL like the following. (Specify the password in clear text form, whether or not encryption is used.)