Posted: 10 Jan 2018 6:57 EST Last activity: 8 Jan 2019 12:51 EST
Concurrent Sessions restrictions limiting Web Mashup
For a project requirement we are implementing Pega Web Mashup (IAC). However also as per security requirements we have defined Concurrent Sessions to 1 in the system rule. Now the User ID created for Web Mashup throws and error due to concurrent session limitation.
Do we have any straightforward resolution for this, where we can exclude Web Mashup users from Concurrent session restriction?
Thanks for sharing, I have reviewed given post. But the issue we are facing is in 7.3 we have already set the concurrent sessions to 1 in System rule.
This same validation is getting applied to the model user created for MashUp limiting the Mashup Model User to one session. We need a way to by-pass concurrent restriction to the model user created for MashUp.
You can specify a whitelist of operators to not be affected by the setting: "You can set up a list of operators to which this setting does not apply using thepresence/maxsessions/operators/whitelistDynamic System Setting."
It worked for me when I added it. It allowed concurrent access for email@example.com when I set the system rule to allow only 1. Can you make sure you are using Pega-Engine as the owning ruleset and make sure you do not have a space after the word default?