Thank you for this write up. I'm a bit confused on the groups though. The OrionGroups claim clearly lists all of a user's security groups. If a matching SAML Group in Orion is found, are those the permissions applied to that user?
Yes. As long as the group names match then whatever access that group has in Solarwinds will be granted to the authenticated user.
Thanks bnpj! The guide was really useful.
Has anyone has any success in getting SolarWinds to work with Azure groups? For some reason, I cannot get the group based authentication to work using the group name, only the group ID. I assume I need to set something in the OrionGroups claim as I see it list the group ID in the attributes in the SAML log but not the group name. So if I add a SAML group with the Azure group ID it works, but not using the group name. If that makes sense
This is what I see in the SolarWinds SAML log...
<Attribute Name="OrionGroups">
<AttributeValue>af49ae14-133c-xxxxxxx-xxxxxxx</AttributeValue>
<AttributeValue>12a4edad-cb88-xxxxxxx-xxxxxxx</AttributeValue>
<AttributeValue>10798acd-8bfc-xxxxxxx-xxxxxxx</AttributeValue> ----> This group ID matches the group in Azure the user is a member of.
<AttributeValue>2ba35399-d435-xxxxxxx-xxxxxxx</AttributeValue>
<AttributeValue>e937e6b5-0569-xxxxxxx-xxxxxxx</AttributeValue>
</Attribute>
FWIW,
I had similar issues. Adding single users worked fine but groups would always fail. After some trial and error, I was able to get the groups to work by changing the group claim from "Security Groups" to "Groups Assigned to the Application".
The groups were created as security groups, so I'm not sure why it wasn't working outside of maybe a timeout or something.
Adding my .02 in case it helps anyone