Cookie Administration For Acs - Alcatel-Lucent OmniTouch Administration Manual

............................................................................................................................................................................................................................................................
possible to modify the domain at the time the cookie is created. Relaxing the cookie
domain increases the scope of the cookie's visibility making it available to a wider
"audience" of web servers.
For example, if a cookie is created by alcatel-lucent1.us.company.com, its domain will
usually be set to alcatel-lucent1.us.company.com. This means that the browser will only
send the cookie to alcatel-lucent1.us.company.com. It will never send it to any other
servers. However, if at the time of creation (when the server sends the cookie to the
browser), the domain of the cookie is set to .us.company.com, the browser will send the
cookie to any server whose domain falls within .us.company.com. such as alcatel-
lucent2.us.company.com or alcatel-lucent3.us.company.com.
Note:
invalid character is "_". Refer to the following Microsoft technote found at
http://support.microsoft.com/kb/275033
"Cookies Are Not Saved If the Host Name Is Invalid."

Cookie administration for ACS

In an OmniTouch ACS stack, each server is administered separately. In a deployment, a
customer may want to use the same admin ID and password for managing all servers in a
stack, or even across sites. The administration interface provides a basic UI navigation
feature for moving from one server in the stack to another. To allow the administration
session credentials to be shared across the servers, the cookie domain needs to be set to
something like ".us.company.com" which is the sub-part of the overall server name that
matches all servers in the stack.
If the deployment does not allow this "seamless" administration navigation throughout the
stack, you can set the cookie domain to the appropriate FQDN (fully qualified domain
name) for each individual server. You can also set it to blank (no value) which has the
same effect as setting it to the FQDN for each particular server. This means that the
administrator will be prompted to login each time they move to a new server in the stack.
............................................................................................................................................................................................................................................................
F - 2
Make sure your domain name contains valid characters. An example of an
8AL90208USAD ed01
November 20, 2008