Comments
-
Sorry, just missed your post before adding to mine. Thanks for the help!
-
Yep, I've built the same VB.NET code and get the invalid creds exception. I tried GetSwisClient.ClientCredentials.UserName.UserName = "Administrator@MyDomain" and GetSwisClient.ClientCredentials.UserName.UserName = "MyDomain\Administrator" My VB.NET client is in another domain but I can use the exact same credentials in…
-
By the way are you doing anything different than what is shown in the .pdf docs as far as what you send as username and password to SWIS when using an 'Orion AD?' I'm having trouble authenticating to SWIS with AD credentials. Non-AD creds work fine. I've tries passing 'domain\username' and 'username@domain' but to no…
-
I figured that. Unfortunately all I get is 'RunQuery failed' error. I've tried to dive deeper down into the exception to get the property that failed but I can't seem to find it.
-
You are quite right. I was trying something different when testing the HTTPS connection. All is well. I think the Orion without HTTPS or AD never worked for me in the first place so my question is answered. Thank you.
-
FYI, the Orion 9.5 user was able to retrieve basic and advanced alerts but received 'RunQuery failed' exceptions when accessing nodes and interfaces.
-
Ah I see it now. It is one level deeper than account listing. Thanks Tom!
-
This happens when I try the NetTcpBinding_InformationService1 on net.tcp://{0}:17777/SolarWinds/InformationService/Orion/ad endpoint with valid AD credentials that haven't been authorized in Orion (via a group or individually). e.g. Account 'Foo\Bar' is valid in AD and has been authorized on Orion: all works well. In my…
-
Update: Still same error with connection using Server type 'Orion.' Works with 'Orion AD'. RemoteCertificateNameMismatch error using 'Orion over HTTPS'. If I continue I get 'Unable to connect to Information Service. The HTTP request was forbidden with client authentication scheme 'Basic.'