After upgrading from VSJ 3.0 to VSJ 3.3 clients fail with clock skew errors. For example:
ERROR 2010-07-06 19:51:42,135 GMT jcsi-logger: Provider protocol error: com.wedgetail.idm.spnego.server.SpnegoException: GSSException: Failure unspecified at GSS-API level (Mechanism level: com.dstc.security.kerberos.KerberosError: Clock skew too great)
The client PC clock is out by more then 5 minutes however prior to upgrading these errors did not occur.
In the previous versions of VSJ we were not checking the clock skew correctly. This was fixed in 3.3 patch 3548 which is why you are seeing it now.
This is expected behavior however there is a JAVA system setting to increase the clock skew value. The default is 300000 which is 5 minutes. So you set it to 600000 it will give you 10 minutes.
© 2025 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center