Problems Reading Keystores After Identity Server Re-Installation; Duplicate Set-Cookie Headers - Novell ACCESS MANAGER 3.1 SP2 - IDENTITY SERVER GUIDE 2010 Manual

15.3.7 Duplicate Set-Cookie Headers

The Access Manager releases previous to Access Manager 3.1 SP1 allowed a colon in the Set-
Cookie header. Because the cookie specifications stipulate that a colon character cannot be used in a
cookie, the Set-Cookie header in Access Manager 3.1 SP1 removes the colon and sets a value
similar to the following:
UrnNovellNidpClusterMemberId=~03~0Bslo~0A~0B~14mop~0C~09; Path=/nidp
A second Set-Cookie header is included with the colon value to allow for backward compatibility
with devices that have not been upgraded to Access Manager 3.1 SP1. The devices requiring this old
style cookie include Identity Servers that haven't been upgraded and any device with an Embedded
Service Provider that hasn't been upgraded. The old Set-Cookie header value looks similar to the
following:
urn:novell:nidp:cluster:member:id=~03~0Bslo~0A~0B~14mop~0C~09; Path=/nidp
Both cookies contain the same information. Setting the two cookies does not impact functionality or
performance.
15.4 Problems Reading Keystores after Identity
Server Re-installation
This can occur if you replace a hard drive and incorrectly reinstall the Identity Server. See
"Reinstalling an Identity Server to a New Hard Drive" in the Novell Access Manager 3.1 SP2
Installation Guide for the correct procedure.
360 Novell Access Manager 3.1 SP2 Identity Server Guide