@NavakanthMannem

1. The idle timeout of requestors in the pool can be configured in the "Requestor Management" landing page in the Pega Designer Studio. The default value is 30 minutes, which means that if a requestor remains idle (i.e., no requests are received for it) for more than 30 minutes, it will be removed from the pool.

2. Pega provides several options for caching authentication credentials, such as LDAP cache or credential cache. These options are available in the "Authentication Service" rule instance. By enabling caching, Pega can reduce the number of LDAP server hits for subsequent requests from the same consumer.

3. It is generally not advisable to keep requestor sessions long without ending them, especially in a Stateful processing mode. Keeping requestors idle for a long time can lead to issues such as memory leaks, increased response time, and potential security vulnerabilities. However, depending on the specific use case and system requirements, it may be acceptable to increase the idle timeout or use other techniques such as requestor pooling to improve performance. It is important to carefully consider the implications of such changes and thoroughly test them before deploying to production.