Clock Tampering in Sentinel Cloud

What happens when the clock is tampered after detaching a license?

If a clock is tampered after detaching the license then the user will continue to use the license untill it gets expired. However another license won’t be able to detach if the time difference (between client machine and SCC server) is more than 15 minutes.

 

What is the error code and description expected when the detaching of license fails due to clock tampering?

In this scenarios, YPS throws error code -3021 Invalid/null authorization header in request (visible in Runtime logs only) and Runtime converts that to 2011 RT_ERR_INVALID_AUTHENTICATION – Authentication Failed. (visible in Runtime application)

 

If time tampering detection can be disabled?

Time tampering detection cannot be disabled.