Hi Kiran,

Thanks for posting on PSC,

Enter a number of seconds after which the system challenges idle browser sessions (for users of this access group), asking users to re-enter their Operator ID and password. This timeout event does not cause session context or clipboard contents to be lost.

If users respond to the challenge and are re-authenticated, they can usually continue processing where they left off, unless the system released locks they held in the meantime, or the system was stopped and restarted.

This setting is also taken into account in a mobile app that is either online or offline. When the timeout value is reached, the user is automatically logged out when they perform any action. They are brought back to the login screen.

Note: This authentication timeout is not related to the timeout/browser value in the prconfig.xml file or Dynamic System Settings, which controls when passivation occurs.

Refer it:-https://pdn.pega.com/sites/pdn.pega.com/files/help_v721/procomhelpmain.htm#data-/data-admin-/data-admin-operator-/data-admin-operator-accessgroup/settings.htm

Kindly notify if it helps you in implementing your business requirement, by marking this post as answered.

Regards,
Asif

Other useful posts:-

https://pdn.pega.com/about-requestor-timeouts

https://pdn.pega.com/community/pega-product-support/question/sso-user-session-timeout

Hope it helps.

Access Group timeouts, also called authentication timeouts, are established in the Settings tab of the access group form. This setting applies only to interactive (browser-based) users. The system may challenge users who have not sent input to the server during a period, forcing them to re-enter an Operator ID and password.

If you want custom authentication you can use of pxSessionTimer section .

For more information go through below article

https://pdn.pega.com/sites/pdn.pega.com/files/help_v719/procomhelpmain.htm#definitions/t/timeouts.htm

Thanks,

Arun