Save of Operator record during authentication process
When an existing Operator logs in, the credentials are evaluated (sometimes by a custom authentication service) and if the authentication succeeds then the Operator record is retrieved. At what point does this Operator record get saved? For example, the pyLastSignon column typically gets updated in the operator table. Is there a specific Activity to look at to see where this is happening? I see that the Operator record can be potentially saved in the InitialProfileSetup activity, but only if there are outdated unavailable times.
Accepted Solution
Pegasystems Inc.
US
Thanks - the requirement is to dynamically switch the user’s primary access group if the user is logging in from a hybrid client (mobile) application. The change can be made, but then it is persisted in the operator record and it affects the user negatively if that user needs to log back into a desktop application. The implementation team has decided to also dynamically switch the user’s primary access group back when the user is logging in from a browser. There are different authentication activities for each situation, and so these two authentication activities have been modified. This appears to be working now.
Accepted Solution
Pegasystems Inc.
US
Thanks - the requirement is to dynamically switch the user’s primary access group if the user is logging in from a hybrid client (mobile) application. The change can be made, but then it is persisted in the operator record and it affects the user negatively if that user needs to log back into a desktop application. The implementation team has decided to also dynamically switch the user’s primary access group back when the user is logging in from a browser. There are different authentication activities for each situation, and so these two authentication activities have been modified. This appears to be working now.