We have IAC based html file for client application and prgateway is configured accordingly. The UserIdentifier present in IAC Div is dynamic in nature and in case if operator not present in PEGA DB then screen is landing to auth page defined in AUTH URL of gateway.
On the Auth login page (/prweb/IAC) if user enter the operator id (with external auth enabled) then system is not allowing the user to login and it’s kind of waiting for ever long.
Please let us know if you face the same situation in any other project and possible resolution you have applied.
Following is the gateway configuration screenshots:
We have applied the similar settings in prgateway which is hosted in DMZ web server to access IAC over internet. And after applying same domain policy we have seen the test connection is successful from internet link of prgateway to backend prweb server (located inside firewall and not exposed to internet).
But in case if UserIdentifier is not passed correctly then default login page is shown, till this point everything is correct, now if we give a valid operator id then system is kind of taking hours to access (even though the requestor is created in backend prweb server) and finally system is hanged.
We have observed that access.log file of the weblogic is randomly getting generated during that time period of login and consuming larger space in the system. below access logs were printed in tons:
Could you/anybody please highlight what could be the issue? Any special prgateway configuration need to be applied or not? We have used the below configuration: