search cancel

Response Header Variable not Set After Policy Server Upgrade


Article ID: 7575


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On


We recently performed a parallel upgrade of our Policy Server from SiteMinder 12.51 to 12.7.

During the test phase, we noticed that some responses (which should set HTTP-Header-Variable using userattributes) are no longer set


Policy Server 12.7 on Windows 2012 R2 Standard


You should note that the User Attribute in Active Directory is case sensitive. As such, "EMAILADRESS" attribute is different than "emailAddress".

For example, you want to set the header variable EMAILADRESS with the content of the user's attribute name emailAddress.

If you set the attribute name as "EMAILADRESS", it will NOT work (the header variable will be empty).



Setting the attribute name as "emailAddress" will resolve the issue (the header variable is set)