Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

error on screen while connect portal to IAC instance



Customer is unable to access the Pega Application through IAC with and without WebSeal

1.  The out of the box Pega IAC functionality is not working
2.  Using WebSeal cannot access the Pega Application through IAC

Error Messages

  1. After configuring the out of the box Pega IAC Gadget and previewing it throws exception:  “There has been an issue, please contact your administrator”
  2. With WebSeal enabled, when accessing the gadget  from a web page, getting the following error:

            Redirection appears to be in a loop, terminating request:!OSGLICPM/$STANDARD?

Steps to Reproduce

  1. After configuring the out of the box Pega IAC Gadget and preview throws exception:  
            “There has been an issue, please contact your administrator”
  1. With WebSeal enabled, Login in GIPORTAL and click 360 view and we will get below error message. The GIPORTAL is the web application and the 360 view is the page where the gadget is displayed

Root Cause

  1. Customer was using a web server in front of the application server hosting the Pega application. Customer was using the default out of the box authentication servlet IAC however in webserver plugin-cfg.xml, they were using mapping servlet name as “IACAuth” used prior to their Pega upgrade from 5.x. to 7.1.9. The mapping servlet entries for IAC was missing
  2. There is a potential architectural issue with the current setup of Gateway. The WebSeal authentication is being triggered twice before reaching the PRPC server. The request traverse from browser to Gateway via WebSeal and from Gateway to PRPC again via WebSeal where it’s failing during 2nd time authentication 


  1. For the first issue of the out of the box Pega IAC functionality was fixed after adding the missing authentication servlet mapping IAC webserver plugin-cfg.xml
  2. Bypass the Gateway and directly access the Pega Server by setting the Gadget parameter "Pega.web.config.gatewayURL" to the relative URL as follows:
        Pega.web.config.gatewayURL = "/prweb/IAC"
        This configuration worked both with and without WebSeal

Published March 16, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us