Cannot find ticket for requested realm while validating credentials

Posted by / 31-Oct-2020 20:46

A last resort is to disable the encryption requirement on the Windows host.

This should only be used for development and debugging purposes, as anything sent from Ansible can be viewed, manipulated and also the remote session can completely be taken over by anyone on the same network.

In this process, a new ticket is created in a temporary credential cache for each host.

This is done before each task executes to minimize the chance of ticket expiration.

This is achieved by encrypting the username and password after authentication has succeeded and sending that to the server using the Cred SSP protocol.

Because the username and password are sent to the server to be used for double hop authentication, ensure that the hosts that the Windows host communicates with are not compromised and are trusted.

Using Win RM with TLS is the recommended option as it works with all authentication options, but requires a certificate to be created and used on the Win RM listener.

TLS 1.2 is installed and enabled by default for Windows Server 2012 and Windows 8 and more recent releases.

There are two ways that older hosts can be used with Cred SSP: Note This certificate configuration is independent of the Win RM listener certificate.

The creates a self-signed certificate and creates the listener with that certificate.

If in a domain environment, ADCS can also create a certificate for the host that is issued by the domain itself.

cannot find ticket for requested realm while validating credentials-14cannot find ticket for requested realm while validating credentials-25cannot find ticket for requested realm while validating credentials-2

Basic authentication can only be used for local accounts (not domain accounts).

One thought on “cannot find ticket for requested realm while validating credentials”