This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

SWIS / SWQL Studio / API - Windows Group Authentication Issue

NightEdition over 3 years ago

Hi All,

One of our SolarWinds NPM 2020.2 instances is experiencing authentication issues with SWIS and SWQL Studio connections.

SWIS and SWQL Studio connections to SolarWinds do not appear to allow authentication of active directory accounts configured for SolarWinds access via "Windows Groups". SWQL Studio simply reports the following...

The Orion log on the primary poller reports the following when such an attempt is made:

WARN SolarWinds.Data.Providers.Orion.OrionAccountValidator - (null) (null) Invalid username or password for user 'DOMAIN\username' via password hash comparison.

Logins to the SolarWinds web front end/GUI authenticate via "Windows Groups" without any issues.

Connecting via SWIS/SWQL Studio using an individual account which is configured within SolarWinds (local Orion or active directory account) also works without any issues.

To rule out an issue with a specific windows group, a new group was created and configured for access within SolarWinds however the issue with SWIS/SWQL Studio connections also occurs with this new group.

We have other similar SolarWinds instances which allow "Windows Group" authentication via SWIS/SWQL Studio without any issues, so we know this authentication method should be possible.

Has anyone had similar issues?

Thanks.

Top Replies

Parents

0 dan_jagnow over 2 years ago

This is a confirmed bug in product. It is being tracked internally as issue CORE-15843. I'm sorry to say that a fix did not make it into the 2020.2.6 release, but it has been associated with multiple customer issues and is getting some attention.
Cancel
Vote Up +2 Vote Down

Cancel

Reply

0 dan_jagnow over 2 years ago

This is a confirmed bug in product. It is being tracked internally as issue CORE-15843. I'm sorry to say that a fix did not make it into the 2020.2.6 release, but it has been associated with multiple customer issues and is getting some attention.
Cancel
Vote Up +2 Vote Down

Cancel

Children

0 edwinhoekman over 2 years ago in reply to dan_jagnow

Hi Dan,
Thanks for letting us know. Hopefully in the next release. Especially with the new expiration on the Orion Individual accounts.
Cancel
Vote Up +1 Vote Down

Cancel
0 planglois over 2 years ago in reply to dan_jagnow

If we are facing issues with it, should we open a case to add to the list so it get hotfixed, or it wouldnt change anything?
Cancel
Vote Up 0 Vote Down

Cancel
0 KMSigma.SWI over 2 years ago in reply to planglois

Preface: This is customer Kevin answering, not SolarWinds Kevin.

I'd open a case and tell the technician that you believe this is related to the above tracking number. Not sure what happens to it after that, but it'll at least get logged.

You can also click "I have this question, too." at the top of this post.
Cancel
Vote Up +3 Vote Down

Cancel