Solarwinds SWIS Powershell - connection error - Get-SwisData : Identity check failed for outgoing message

Hi, I'm trying to utilize the SolarWinds SWIS powershell module but I'm having trouble when trying to run the following query and I'm having trouble finding any articles that explain what is happening or how to resolve it. If anyone can shed any light on this issue it would be much appreciated!

$OrionServer = "SOLPOL.domain.local"
$Username = "admin-swis-powershell"
$Password = "password"

$swis = Connect-Swis -Hostname $OrionServer -Username $Username -Password $Password

$query = "
SELECT
Nodes.Caption
, Nodes.URI
FROM Orion.Nodes AS Nodes
"

$nodes = Get-SwisData -SwisConnection $swis -Query $query

Get-SwisData : Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was
'SolarWinds-Orion' but the remote endpoint provided DNS claim 'SOLPOL.domain.local'. If this is a legitimate
remote endpoint, you can fix the problem by explicitly specifying DNS identity 'SOLPOL.domain.local'' as the
Identity property of EndpointAddress when creating channel proxy.
At line:1 char:10

Find more posts tagged with

connection error

Identity check failed

PowerShell

Accepted answers

All comments

Zerillis

To add to the complexity for this

Domain 1 - Solarwinds main platform/DB engine and primary poller

Domain 2 - Additional poller - I am trying to connect from this poller to swis powershell.

Domain 3 - Additional poller

KMSigma.SWI

I can't see why the certificate would be causing an issue, but then again, I can't see why it would not. Are you trying to connect to one of the machines themselves or from another machine?

The authentication mechanism you are using is via the Orion Credentials (and not AD-integrated), so I can't see how that would cause an issue. You might want to check on the SolarWinds Information Service log (C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log) on your target machine and see if it's showing anything unusual.

Just as a guess, if this is an old set of servers (like very old), you might want to check to see if they have multiple copies of the SolarWinds-Orion certificate installed. I can't see that it would try and use the old certificate instead of a new one to build the secure channel, but I guess it might.

Zerillis

Thank you for the reply - really appreciated.

Should I be able to connect to any poller to access the information service?

from 'Domain 2 - Aditional poller' I've tried to both connect to its self and the primary poller.

Zerillis

I checked the certs on the additional poller, in Local Computer -> Personal

we have 3 certs

SolarWinds Agent Provision - ....
Solarwinds-Orion
Servername

KMSigma.SWI

If you are connecting from one of the Orion Servers, you can skip the username/password and connect via certificate.

$SwisConnection = Connect-Swis -Hostname "OrionServerName" -Certificate

Get-SwisData -SwisConnection $SwisConnection -Query "SELECT Caption, IPAddress FROM Orion.Nodes"

Can you check the expirations and stuff on the 'SolarWinds-Orion' certificate?

Get-ChildItem -Path Cert:\LocalMachine\My | Where-Object { $_.FriendlyName -eq 'SolarWinds-Orion' } | Select-Object -Property FriendlyName, Thumbprint, @{ Name = "Start Date"; Expression = { $_.NotBefore } }, @{ Name = "Expiration Date"; Expression = { $_.NotAfter } }

acurrent

is solpol.domain.local the FQDN of the polling engine? Also did you add command 'import-module swispowershell' prior to the connection string?

Also you can try running on a polling engine directly using localhost as the hostname to see if it works

james.kluza

I know this was a bit ago, but do you know which version of PowerShell you were using? I just ran into this issue for the first time and the environment is using v7.2 While another environment using v 5.1.14393.4583 runs no problem. I'm wondering if there isn't something in the latest versions of PowerShell that isn't compatible with the current SWISPowerShell module.

Additionally, you won't find anything in the InfoService logs on these errors since this is a client based no-go scenario.

KMSigma.SWI

@james.kluza - you may want to check the version of the SwisPowerShell module you are running.

I tweaked the 00_Auithenticate.ps1 script I posted for THWACKcamp this year to output the version of PowerShell and the version(s) of the SwisPowerShell module.

The output looks like this now:

PowerShell credential request
Enter Orion Credentials for '[Redacted]'
User: KMSigma
Password for user KMSigma: ************
WARNING: We're successfully connected to 'NOCKMSMPE01V' using PowerShell 7.2.2 and SwisPowerShell 3.1.0.343

I documented how I setup my environment in a sample chapter of an upcoming eBook.

james.kluza

Yeah so it isn't a PowerShell version issue. I forgot where I had done the original testing was from my macOS machine with PowerShell and the SWISPowerShell module installed and I have those exact versions. The module was just installed in failing environment so I'm sure it is the latest as well. Something environmental then causing the issue.

KMSigma.SWI

The SwisPowerShell module does rely on the SolarWinds Information Service (SWIS), so if there are issues with that server, that's likely the cause of your problems.

bobmarley

Possibly try what is shown below. It will attempt to log in with whatever credentials your PC is currently using. Replace "YOURORIONSERVER" with your server name

Import-Module -Name SwisPowerShell
$swis = Connect-Swis -host YOURORIONSERVER -Trusted

james.kluza

This seems to be an endpoint resolution issue, not necessarily with authentication.