Question
US Department of Veteran Affairs
US
Last activity: 4 Oct 2018 13:54 EDT
Concurrent session
I would like to know to control concurrent sessions in Pega. Currently we can open more than one session for the same user and we wanted to control to open only active session all the time.
Message was edited by: Lochan to add Category
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems
US
Although there may be way to do this, I suggest you think about why you need this, since there are other checks in place that may make such a restriction unnecessary.
For example, if you are using standard locking on work objects, even if you allow the same user to log in more than one requestor, only one of the requestors will be allowed to open any given assignment. If this standard restriction is sufficient, you needn't worry about the multiple logins.
/Eric
US Department of Veteran Affairs
US
We are seeing issues, we wanted to control concurrent session, can you provide me a steps that need to be done we are on 7.1.8
Pegasystems Inc.
IN
Hello,
This should work in 7.1.8 . However, I need to mention a crucial limitation with this setting, which may make the approach completely useless
The use of this setting will only inspect the CURRENT node's requestors, and would only prevent user login if there was another session present on the same node.
If the same user was logged into another JVM- this process would not see the requestor lists of the other nodes and would not prevent the second login on disparate node(s).
As far as I know., in PRPC 7.1.8 it has no mechanism for preventing concurrent logins in a multi node environment.
But it is definitely addressed in 7.2 . Nagarjuna Kurri , Any thoughts ?
US Department of Veteran Affairs
US
Hi Santanu,
here is the scenario, users will be allowed to login 3 times after that we want to restrict the user, any suggestions?
Pegasystems Inc.
US
Hi Venkat,
If you are in 7.2, you can disable concurrent sessions. Below is the process you need to follow to do that.
- Create a new System record
- Create requestor types using the new system name (without these the system won't start).
- Open the new system record and using the clipboard editor change the value of pyConcurrentSessions to none.
- Click save on the form showing this instance
- Modify prconfig to use the new system name.
- Redeploy prconfig on a restart of the system.
Please revert back if you face any problems.
NOTE: You have to edit the system record from the clipboard before saving it(i.e when it is in the new record state)
Pegasystems Inc.
US
Hi Venkat,
Following the above steps may halt operators logging in for the first time as well due to a bug in 7.1.8 which is fixed in 7.2.
However, those steps will only work in case of single node environments. If your planning to achieve this on a multi-node environment, we have an enhancement request(FDBK-11403) ongoing.
--Ravi
US Department of Veteran Affairs
US
Hi Ravi,
is there any document or any step by step process to perform below steps
If you are in 7.2, you can disable concurrent sessions. Below is the process you need to follow to do that.
- Create a new System record
- Create requestor types using the new system name (without these the system won't start).
- Open the new system record and using the clipboard editor change the value of pyConcurrentSessions to none.
- Click save on the form showing this instance
- Modify prconfig to use the new system name.
- Redeploy prconfig on a restart of the system.
Pegasystems Inc.
US
Hi Venkat,
I don't have any document as such. I can provide you detailed steps with screenshots but they might not be useful for you as due to the bug in 7.1.8 you'll end up preventing all the logins to the system rendering the system useless until you change the system name back and restart the system
Pegasystems Inc.
US
Hi Venkat,
Please follow the below steps for stopping concurrent sessions in a single node:
- Go to instances of record type system(records explorer>sysadmin>System).
- Open any existing system name and save as that into any name you desire.(let it be abc)
- Open clipboard for that newly created rule and go to page pySaveAsResults of class Data-Admin-System.
- Now change the pyConcurrentSessions value to none from unlimited.
- Save the clipboard and save the rule form.
- Now we have to create "requestor types" for this newly created system name.
- We have to create 4 requestor types namely App, Batch, Portal, Browser.
- For this we can save as the existing requestor types to point to new system name.
After creating all the requestor types we need to change the prconfig.xml to point to new system name. This you can do by the following statement: <env name="Identification/SystemName" value="abc"/>
NOTE: Please check if the requestor types are created properly. Without the requestor types properly created you cannot access the system. You can see all the requestor types from System-General Landing page(Designer studio>System>general>Systems,nodes and requestors).
Please revert back if you are struck at some point.
--Ravi.
US Department of Veteran Affairs
US
Thanks for your reply ravi. I implemented the above steps, but we are able to multiple session after that, any suggestions.
Pegasystems Inc.
US
Hi Venkat,
Can you please check if the property pyconcurrentsessions for the system name rule is set properly. (check it in the clipboard)
--Ravi.
Evonsys
NL
Hi Ravi,
Can you please help me for the below scenario, what are the steps for the multi-node environment.
If your planning to achieve this on a multi-node environment, we have an enhancement request(FDBK-11403) ongoing.
Thanks in advance,
Nagamani
PEG
PL
You could use custom authentication to fulfil this requirement. If you have your own authentication activity then you could have a property in code-security where you could maintain the counting.
Pegasystems Inc.
HK
Venkat
One of the my clients have the same requirement on the SUS(Single User Session) control. And it' s been implemented by using the customized session table(DT) to control the below information
Remote IP address
Operator ID(pyUserIdentifer)
Login Application (AG)
The SUS enforcement could be done during the operator logon.
An alternative solution, you can try to leverage JMX API to configure the same but the debugging will take a lot of time and not easy to control/purge.
Hope this helps..
Cheers,