Ajax returns a 302 code as it should not in Web Agent

Products

• CA Single Sign On Secure Proxy Server (SiteMinder)
• CA Single Sign On Agents (SiteMinder)
• CA Single Sign On Federation (SiteMinder)
• CA Single Sign On SOA Security Manager (SiteMinder)
• CA Single Sign-On
• SITEMINDER

Issue/Introduction

 

When running a Web Agent and one application running an Ajax code, this one returns a 302 code to the Web Page when it should not.

 

Resolution

To handle Web 2.0 code as Ajax, implement the following Web Agent ACO parameter:

   WebAppClientResponse

This ACO parameter is designed mainly to integrate to redirect users when a session timeout occurs (1).

 

Additional Information

(1)

    Apply SiteMinder Behavior to a Web Application Client