Web Agent Guides › Web Agent Configuration Guide › Troubleshooting › Browser Is Not Submitting Cookie

Browser Is Not Submitting Cookie

Symptom:

My browser is not submitting the cookie to my other web server after I authenticated at the first server.

Solution:

Check that the CookieDomain field for single sign-on contains at least two periods and that it is a subset of the server name, as in the following example:

.mycompany.com cookie domain works for all machines that end in .mycompany.com. Although it is possible to access a local web server without the full domain name, this method cannot generate the submission of a cookie by your browser. Therefore, the URL http://www/index.html gets the web page, but cannot match the cookie domain, so a cookie is not submitted (you may be asked to reauthenticate).

If you are using a country code, for example, www.company.abc.uk, make sure there are three periods in the URL. Also, be aware of the following:

• Check that you specified the fully qualified domain name in the browser.
• If you set CookieDomain to none, the Web Agent creates cookies only for the server that issued them.
• If you leave CookieDomain blank, the Web Agent gets the cookie domain from the HTTP_HOST header based on the value of the CookieDomainScope parameter.
• When the CookieDomainScope parameter is set to 0, the Agent chases the most specific cookie domain for the host without making a server-only cookie. This means that the host myserver.netegrity.com yields a domain of netegrity.com, and myserver.metals.ge.com yields a cookie domain of .metals.ge.com. If CookieDomainScope is set to 2, the cookie domain would be .netegrity.com and .ge.com respectively.