Specific requestor timeout
Hi,
we have a situation where a special user is used to check application status by a 3d supervision application, that runs frequently.
This user is used to snapstart an activity, which has "may start?" checked but not "Authenticate?".
We need that the system will not have a lot of requestors for supervision. For that I see 2 options:
1- (preferred) reuse the same requestor whenever the activity is called. Perhaps there is a system setting or a prameter to pass in the snapstart but I can not figure it out.
2- set a short timeout for these requestors without afecting final user requestor timeout. The authentication timeout from access group does not apply while we do not use authentication. The passivation timeout applies to all users.
Have you an Idea how this can be done ?
Thank you for your help.
Pegasystems Inc.
US
If the activity doesn’t need authentication and you are ok with an unauthenticated requestor, then you can pass query parameter “pzAuth=guest” which avoids authentication. Such unauthenticated or none requestors are normally removed within a minute
Sopra Group
FR
Thank you Pradeep, that works. But indeed, there a issue executing activity without auth.
What about if we turn it with authentication ? Can we then reuse the requestor ?