I have an exitsingIAC implementation in production with siteminder authentication. What I have seen is IAC is only able to authenticate or rather find the authentication activity when the access group in the browser requestor has the same application as the one that you are giving in PegaAppName. This works fine. Now that I am building another application on the same platform, I am not able to make this work as application is different and I cannot have another requestor on the same server.
Is this is as designed by Pega or is this an issue or am I missing something?Browser requestor should use an access group to just authenticate the user and after that should use the appname from the gadget. Using the same application name for unaunthenticated request does not seem to be right.
Let me know if there is a way to solve this. I will also open an SR to confirm the behaviour.
Hi, as you are already pursuing this with a support request, they will have better details, in the meantime recommend the following approach.
You can have more than one requestor on a server.
Typically you will create a unique operator/requestor record for authentication. On that operator record you will specify one specific access group that points to your application. In your scenario, try to create the three pieces operator record, access group and application.
I have small question ,whether PRPC will create a new operator ID when we use an IAC authentication?
Scenario: i am using an Java application and in that Java application i will be logging with Siteminder authentication. After login into the Java applicaton there is a tab on which i am calling my PRPC application , in this case whether i need to create an user /Opertor ID in the PRPC table?