An issue may be encountered where authentication to Unix/Linux Environments fails using Kerberos credentials, though the keytab and other details are confirmed to be correct.
This issue will affect Dataset operations (SnapSync, Provision, Refresh) as well as Environment Disovery and Refresh.
- An enabled Kerberos KDC configuration
- One or more Environments configured with Kerberos credentials
- Delphix Engine version is 18.104.22.168-22.214.171.124
Applicable Delphix Versions
- Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases 6.0 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
This behavior is the result of incorrect parsing of the Kerberos authentication ticket expiration date on the Delphix Engine which may cause the ticket to be updated too frequently or not frequently enough, the latter resulting in login failures. The behavior is ultimately resolved in 188.8.131.52 which is generally available for upgrade.
Upgrades from 184.108.40.206 and later to 220.127.116.11 do not require Support intervention; the upgrade can be applied as soon as is convenient, and may not require any VDB downtime. Details of the target Delphix release and upgrade instructions should be reviewed for further detail:
The issue is referenced by DLPX-73611 in the Fixed Issues segment of Release Notes.
The following event may be encountered during any job that requires Environment authentication using Kerberos credentials as mentioned earlier in the article (Dataset operations or Environment Discovery, Refresh).
messageAction: Make sure that the host user and password are correct, and that the Delphix Connector is properly registered with the Delphix Engine. messageCode: exception.ccc.authenticate.failed messageCommandOutput: net.schmizz.sshj.userauth.UserAuthException: Exhausted available authentication methods messageDetails: Could not log into "<ENVIRONMENT NAME>" with the provided username and password.