No SMSESSION cookie with CustomIPHeader in SPS behind a Load Balancer?
search cancel

No SMSESSION cookie with CustomIPHeader in SPS behind a Load Balancer?

book

Article ID: 278041

calendar_today

Updated On:

Products

SITEMINDER CA Single Sign On Secure Proxy Server (SiteMinder)

Issue/Introduction

When running CA Access Gateway (SPS) as an OAuth client, the SPS Agent gets the correct Client-IP value, but the Java OAuth Service doesn't seem to receive it.

So, the session is created with the Load Balancer IP instead of the Browser IP.

Environment

Component: SMSPS (CA Access Gateway)
Environment: Applicable to all the supported releases

Resolution

Enable the CA Access Gateway (SPS) to pass the X-Forwarded-For value to the Java processing on the CA Access Gateway (SPS) and Tomcat (mod_jk) by following the steps in the documentation.

- Navigate to the following path on the machine where Access Gateway is installed:

         Location: accessgateway_installation\CA\secure-proxy\httpd\conf

- Open " httpd.conf " file and make the following changes:
       
          - Uncomment the following entry:

LoadModule setenvif_module modules/mod_setenvif.so

           - Add the following entry below the entry you uncommented in Step

SetEnvIfNoCase X-Forwarded-For (.+) JK_REMOTE_ADDR=$1


------ Document reference: 

Log Client IP in Logs