KCM: reset last_request_time on any activity
As all the activities are being handled by the kcm responder itself and
not by responder's common code, we have to take care of re-setting the
last_request_time by ourselves here.
Without this patch, the responder would be shot down after reaching the
idle_timeout with activities happening or not.
Resolves:
https://pagure.io/SSSD/sssd/issue/3633
Signed-off-by: Fabiano FidĂȘncio <fidencio@redhat.com>
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>