Hi James, Please make sure that all Groups you are trying to save are available on the AD server. The difference is when you are saving Environment it checks all associated Teams against AD.
UI: https://github.com/Scalr/scalr/blob/45ee1379f061a0122557edcdd22fc58a7459fb95/app/src/Scalr/UI/Controller/Account2/Environments.php#L253 API: https://github.com/Scalr/scalr/blob/master/app/src/Scalr/Api/Service/Account/V1beta0/Adapter/TeamAdapter.php#L117 Regards, Vitaliy Demidov On Sat, Oct 22, 2016 at 4:53 PM, James Smith <[email protected]> wrote: > I've configured Scalr to use LDAP for authentication and that part is > working. Afterward, I enabled APIv2 and that part is also working - > although I had to add scalr.connections.ldap.user and > scalr.connections.ldap.pass to the config; this is not documented in the > APIv2 docs (as far as I could tell), only the APIv1 docs. > > Now, LDAP log-in works fine and so does API access. However, if I try to > add an LDAP group to an environment, or make any other changes to an > environment that already has LDAP groups attached, I get an error "Team > '<LDAP group name>' is not found on the directory server". I can work > around this by commenting out the ldap user and pass from the config, but > this disables API access until I'm finished. > > Has anyone else seen this issue, or have I misconfigured something > somewhere? > > -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
