My Oracle Support Banner

Requesting kerberos TGT with OKINT errors with okinit: Clock skew too great in (Doc ID 2312008.1)

Last updated on JANUARY 22, 2020

Applies to:

Advanced Networking Option - Version and later
Information in this document applies to any platform.


 Requesting kerberos TGT for user through OKINIT fails with okinit: Clock skew too great


[07543]/refresh/home> okinit -e 23 user123

Kerberos Utilities for Linux: Version - Production on 23-SEP-2017 03:53:23

Copyright (c) 1996, 2014 Oracle. All rights reserved.

Password for user123@XXXX.SAMPLE.COM:
okinit: Clock skew too great


okinit trace show below

nauk5la_get_in_tkt: Returning 37: Clock skew too great
nauk5la_get_in_tkt: exit
nauk5zi_kinit: Getting TGT failed: Clock skew too great
nauk5fq_free_principal: entry
nauk5fq_free_principal: exit
nauk5fq_free_principal: entry

Setting SQLNET.KERBEROS5_CLOCKSKEW=300 or 1200 does not help. In this case we see a significant time drift between the linux (database server) and the active directory server.


 No changes. Kerberos authentication is under initial stage of configuration.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.