Re: Can't add LDAP group to environments when APIv2 is enabled

Yes, community version 5.11.22. The groups I'm trying to add do exist on the directory server, and the ldap user in the config has access to search the ldap server. On Saturday, October 22, 2016 at 10:43:44 AM UTC-5, DicsyDel wrote: > > Hi James, > > Are you using Opensource scalr? > > On

Re: Can't add LDAP group to environments when APIv2 is enabled

Hi James, Are you using Opensource scalr? On Saturday, October 22, 2016, Vitaliy Demidov wrote: > 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

Re: Can't add LDAP group to environments when APIv2 is enabled

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:

Can't add LDAP group to environments when APIv2 is enabled

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

Re: Scalarizr agent issues

Quite correct, Marc. I found a correlation between very high network congestion internally and both the stuck pending and stuck initializing. For the stuck pending systems, if I ssh into the system and manually upgrade the agent then restart, it proceeds to the next step. This is an