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

IAC : authentication not being executed

SA-24864

Summary



User has two different applications on one server and those two applications are not dependent on each other. With their latest release, in Application1, they are trying to load a screen from Application2 using IAC. They observed that during this the IAC authentication is not being executed at all. They are facing display error in the Application 1 screen.


Error Messages

  1.  IAC authentication is not being executed at all
  2.  In application 1 screen, we are seeing display error message.


Steps to Reproduce



From  Application 1 screen, try to load a screen from Application 2 using IAC gadget code.

Root Cause



User was not using the gateway in their setup. They are usingthe  gateway url as pega.web.config.gatewayURL= "/prweb/IAC/";

However in their gadget code they are setting the systemid parameter as pega.web.config.systemID = <Gateway system id name>

Note: If both of the applications reside on the same server and the user first logs into the server and launches application 1 which displays Application 2 through IAC gadget code, then the authentication won't be triggered. Because the session id is generated and remains same when user first logs into the server. This is expected behavior. 


Resolution



Remove the parameterr "pega.web.config.systemID"  from the gadget code when not using the gateway.
Suggest Edit

Published July 2, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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