Just one thing to make sure, if you have the latest hotfixes for Orion you also need the latest SWQL studio - do you have the latest SWQL studio?
Also, are your AD users added as groups or individual accounts? I see this behavior at other places with group accounts.
We tested with latest version of SWQL and it still does not work. The API access via Python SDK is also not working for AD Group Users. So I guess the issue is not with SWQL but with Core or Information service API.
We dont use individual accounts as there is few many users who need API access. Ex: Users use scripts to mute/manage multiple nodes as part of a Change
Also noticed, when I add a new Orion local user it has only access to the Orion scheme and not to NCM, Cirrus etc. But older local accounts can access all schemas in SWQL.
Looks the whole authentication for API's seems to be mess for me. Is there a way to reset the stuff? like a clean slate and start again
Wasn't there something and users SIDs being empty in the database?
I faced missing Account SIDs in Feb 2022 and I had around 20 users affected. It got fixed by running the powershell script that was provided in the forum.
This time it seems to be a different issue, as all AD group users are affected.
Might want to check if for some reason the SID changed (i.e.: there was an AD migration of some sorts).
If the SIDs are still the same, I would try converting a user who is a member of a an affected security group:
If they can authenticate that way, you've at least eliminated a variable in chasing down the root cause.
I got the Solarwinds Support team to confirm that this is a new bug in the recent release and they are aware of it.
We have 20+ users who need API access and hence adding them directly is not a viable solution, but a good work around.
Also, the security guidelines in the Enterprise restrict use of direct access.
Hi Pramod.Paul.Jose,
Did you manage to get any further clarity from Solarwinds Support regarding this bug?
I raised a ticket as well but got shot down by Support ...
"The Orion SDK and API use is not a component of the SolarWinds licensing model and as such, does not fall under the coverage of Technical Support."
Thanks.
Tell them it is a core bug. JIRA Case: CORE-15843
Then refer them to this thwack link. Even though it is outside the Normal support as it is Orion SDK/API, they should have basic knowledge on what are the known bug within the product.
thwack.solarwinds.com/.../swis-swql-studio-api---windows-group-authentication-issue
I reopened my case and after several back and forth with 2 different Support engineers, especially after a lengthy speel about "caring for your paying customers" and the fact that CORE-15843 is over a year old (possibly 2 years), they've requested logs from me.
Not getting my hopes up yet but lets see how much further this goes. Cheers.
Most probably they would be checking the SWIS logs and check the NULL value on the DB.
Most probably they would be checking the SWIS logs and check the NULL value on the DB.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.