Concurrent Sessions restrictions limiting Web Mashup
Hi Team,
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?
Accepted Solution
Pegasystems Inc.
US
Hi SK,
It worked for me when I added it. It allowed concurrent access for [email protected] 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?
Pegasystems Inc.
IN
Hello Suchira,
Have you reviewed the below article on Concurrent session general configuration. It might give you some pointers.
https://collaborate.pega.com/question/concurrent-session
Thanks!
EvonSys LLC
GB
Hi Gudam,
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.
Thanks
Pegasystems Inc.
US
Hi Suchira,
Take a look at this article: https://community.pega.com/sites/default/files/help_v731/procomhelpmain.htm
Hi Suchira,
Take a look at this article: https://community.pega.com/sites/default/files/help_v731/procomhelpmain.htm
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 the presence/maxsessions/operators/whitelistDynamic System Setting."
Can you give that a try?
EvonSys LLC
GB
Hi Brad,
We were able to solve the issue by adding this configuration at the prconfig file. But for some reason this didn't work when applied as a DSS. Need to check on that further.
Thanks, SK
Pegasystems Inc.
US
Hi SK,
If you were able to add the setting in the prconfig.xml file and it worked, then the DSS entry probably needs to be added as follows:
prconfig/presence/maxsessions/operators/whitelist/default
Thanks,
Brad
EvonSys LLC
GB
Hi Brad,
I'm afraid even this didn't work with a DSS. Is there any additional settings that we have to apply. As far as my knowledge we only need to create the DSS and set values.
Thanks, SK
Accepted Solution
Pegasystems Inc.
US
Hi SK,
It worked for me when I added it. It allowed concurrent access for [email protected] 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?
EvonSys LLC
GB
Hi Brad,
It worked this time, when Pega-Engine is given as owning ruleset. Also the DSS doesn't seem to pick up on the fly. I had to restart to make affect the white-listed users in the DSS.
Thanks, SK