1–Disable Cookie Encoding (Sun Java System Access Manager 7 2005Q4 Deployment Planning Guide)

Sun Java System Access Manager 7 2005Q4 Deployment Planning Guide

1–Disable Cookie Encoding

On each host server that is running an Access Manager instance, disable cookie encoding:

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, set the encodeCookies property to false. For example:
```
<sun-web-app>
<property name="encodeCookies" value="false"/>
...
</sun-web-app>
```
If 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.