This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion


Hello All,

I've just created a new SAML Group login and i'm using the fully distinguished name from AD. I'm only doing this because when I used the CN name it would not let me login to Solarwinds with the SAML group name. Weirdly when I use the fully distinguished name it crashes Solarwinds telling me it cannot use commas, but as you can see below its created the group but with no editable permissions. So I can login read only to Solarwinds.

I think i've found a bug! emoticons_happy.png


Here is the group (below) that is created despite the obvious error above. When I try to edit the permissions it comes up with the above error again.


Any ideas how to fix this?

  • Today I had a conference with SolarWinds support. 
    The specialist acknowledged the "commas in group names" bug and commented that there is a fix planned for that. He could not tell when exactly it will be released but at least there is a plan. 
    He also told me that he would link the support ticket with the bug ticket, which is nice and could speed up the release of a fix. THIS is the page where we can look for new versions and what they fix.

    The workaround is to create the group with commas anyway (like "cn=groupname,ou=groups,"), then ignore the bug and change the permissions for that group directly in the database (SolarWindsOrion.Accounts). Some are very intuitive: 
    - AllowAdmin
    - AllowNodeManagement
    - AllowMapManagement
    - AllowCustomize, etc

    I am happy with this workaround, as I can implement this in the server and will be transparent to users. 

  • Thats good news! Sounds like we might have a fix at some point then...

Reply Children
No Data