search

solarwinds / OrionSDK

SDK for the SolarWinds Orion platform, including tools, documentation, and samples in PowerShell, C#, Go, Perl, and Java.
https://thwack.com/OrionSDK
Apache License 2.0
397 stars 139 forks source link

Suddenly unable to connect using AD credentials - SWQL Studio 2.5.0.214 #290

Open Brianracerboy opened 3 years ago

Brianracerboy commented 3 years ago

Recently our Octopus to SW muting step started failing and I confirmed the cause is because the SWQL Studio is now unable to connect using the AD Service account we created. This was working fine previously. I am able to login into Solarwinds with the domain account without issues. I confirmed on the Solarwinds Orion side everything is fine. SWQL Studio log files show the following below. Any help would be appreciated.

2021-06-30 14:46:52,095 [1] ERROR SolarWinds.InformationService.Contract2.InfoServiceProxy - An error occured opening a connection to the orion communication service. System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. ---> System.ServiceModel.FaultException: An error occurred when verifying security for the message. --- End of inner exception stack trace ---

Server stack trace: at System.ServiceModel.Channels.SecurityChannelFactory1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState correlationState, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout) at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout) at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout) at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open()

Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at System.ServiceModel.ICommunicationObject.Open() at SolarWinds.InformationService.Contract2.InfoServiceProxy.Open()

njoylif commented 3 years ago

I also am having problems with AD creds into API. looking forward to quick resolution. EDIT - My issue appeared when upgrading to 2020.2.6. will create new issue as now contemplating, probably not the same.

Brianracerboy commented 3 years ago

I also am having problems with AD creds into API. looking forward to quick resolution. EDIT - My issue appeared when upgrading to 2020.2.6. will create new issue as now contemplating, probably not the same.

I believe there is a known bug with AD and 2020.2.6 I recently read about. The only way I got mine to work again so far is by going back to the Orion user account.