Question
WorldBank
US
Last activity: 19 Jun 2017 13:59 EDT
Access Group Timeout not enforcing with Custom Authentication
Team,
We have custom authentication implemented with AZURE AD. We are unable to enforce Access group Timeout. Should we need to configure timeout anywhere else?
Thanks in Advance!
Cognizant Technology Solution
US
If you are using SSO, then it might be due to timeout mismatch with the Identity Provider. But if both time out matches, then you should check come configuration settings as well. Use the below link for information on PRConfig entries related to time out.
https://pdn.pega.com/use-pegarulesxml-setting-control-user-timeout-websphere
As an alternativeYou may try to embed the section named pxSessionTimer anywhere in your portal section(Best place is portal header). While including this section, specify the parameters properly. One of the parameter is to specify the time out time.
Pegasystems Inc.
US
If you are using custom authentication please look at the Custom Tab of your AuthService record. There you will see a check box for "Use PegaRULES Timeout". Only when this is selected is the timeout activity run on the next user action if a timeout, based on the Accessgroup setting (>0), has occurred.
If using SAML then the same "Use PegaRULES Timeout" is in the advanced section at the bottom of the SAML AuthService rule record.
WorldBank
US
Thank you Chris.
Timeout is not happening even though we check "Use PegaRULES Timeout" checkbox in the Auth Service record.
Pegasystems Inc.
US
The timeout will occur on a user action. So if your timeout is 30 minutes and you do no actions that trigger a request to PRPC for over 30 minutes you should see your timeout activity running the next user action that triggers a request to PRPC. If you're testing timeouts don't use a really low value, at least 1 minute in the AccessGroup setting.
You may need a pxSessionTimer configured as well but we will get to that later.
WorldBank
US
We are using 2 mins(120secs) for testing the timeout. No actions were being done for 3 minutes after logging in and checking. But the timeout activity is not being triggered.