Discovery credential error: authentication failed for target device

The credential record has expired passwords or keys that are no longer valid on the target device, often due to password policy changes or manual credential updates on the target system. (high likelihood)

The credential type or authentication method configured in ServiceNow does not match what the target device expects, such as using basic authentication when the device requires certificate-based authentication. (high likelihood)

The credential alias is incorrectly mapped or the credential record is missing required fields like username, password, or authentication keys. (medium likelihood)

Network connectivity issues or firewall restrictions are preventing the MID Server from reaching the target device on required authentication ports. (medium likelihood)

The target device has account lockout policies that have temporarily disabled the credential account due to previous failed authentication attempts. (low likelihood)

Step 1: Navigate to Discovery > Credentials and locate the failing credential record to verify all required fields (username, password, keys) are populated and current.

Step 2: Test the credential manually by attempting to connect to the target device using the same authentication method and credentials outside of ServiceNow to confirm they work.

Step 3: Check the ECC Queue (System Diagnostics > ECC Queue) for detailed error messages and examine the MID Server logs for additional authentication failure details.

Step 4: Verify the credential type matches the target device requirements by checking Discovery > Credential Types and ensuring the correct authentication method is selected.

Step 5: Update the credential record with current authentication information and test the connection using Discovery > Test Credential functionality.

Step 6: If using SSH keys or certificates, verify the key format is correct and the public key is properly installed on the target device.

Step 7: Check network connectivity from the MID Server to the target device on required ports and verify no firewall rules are blocking authentication traffic.

Step 8: Re-run the Discovery against the target device and monitor the Discovery Status table to confirm successful authentication.