Member since
07-16-2017
12
Posts
2
Kudos Received
1
Solution
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 8853 | 05-08-2024 02:43 PM |
05-08-2024
02:43 PM
For doc purpose and if it could be helpful to someone We took krb5.ini that was used at the CDP cluster and saved it to client WIN server We used LogLevel=6 LogPath=<some-path> in our jdbc URI to enable trace level log Based on findings from the trace level logs java.security.auth.login.config was pointing to an incorrect login module. Since we turned on memory based cache, removing pointer to the java.security.auth.login.config forced correct tgt ticket to be picked. We did not opt for a custom jaas.conf either. There were minor tweak of domain & realm value. This resolved our issue.
... View more