1–Disabling Cookie Encoding (Sun Java System Access Manager 7.1 Postinstallation Guide)

Sun Java System Access Manager 7.1 Postinstallation Guide

1–Disabling Cookie Encoding

On each host server that is running an Access Manager instance, disable cookie encoding as follows, depending on the web container:

If Web Server is the web container, make sure the following property in the AMConfig.properties file is set to false (which is the default value set by the Java ES installer):
```
com.iplanet.am.cookie.encode=false
```
In the sun-web.xml file in directories that begin with https-, set the encodeCookies property to false. For example:
```
<sun-web-app>
<property name="encodeCookies" value="false"/>
...
</sun-web-app>
```
If Sun Java System Application Server, BEA WebLogic, or IBM WebSphere Application Server is the web container, set the following property in the AMConfig.properties file to false:
```
com.iplanet.am.cookie.encode=false
```

The Access Manager client should not do any cookie encoding or decoding. A remote SDK client must be in sync with the Access Manager server side settings, either in the AMConfig.properties file or the web container’s sun-web.xml file.