Symantec Access Management

Expand all | Collapse all

New WebAppClientResponse ACO Parameter

Jump to Best Answer
  • 1.  New WebAppClientResponse ACO Parameter

    Posted 09-04-2012 11:29 AM
    We have an application that makes a large number of AJAX calls to display report data to the user. These calls fail when the client receives a 302 to the cookieprovider. It is not practical to use the OverLookSessionForMethodsURI or URL parameters in this case because of the number of resources that exist.

    Has anyone had success implementing the new ACO parameter WebAppClientResponse in a r12.5 agent? Will this address prevent the session creation/update issue we have with this application?



  • 2.  RE: New WebAppClientResponse ACO Parameter

    Posted 09-10-2012 03:44 PM
    Hi All,

    Any ideas here for Jeff?


  • 3.  Re: New WebAppClientResponse ACO Parameter
    Best Answer

    Posted 05-23-2017 07:52 PM

    I know you must have moved on from this ...but in case if any one is looking for solution on how to use this , they can refer to this blog :

    Tech Tip - CA Single Sign-On:Web Agent:: Web 2.0 Support