Vitaliy, Brilliant. I should have seen. Yes, it works great.
On Saturday, January 16, 2016 at 11:14:38 AM UTC-7, Vitaliy Demidov wrote: > > Hi Jay, > > Actually workflow may look like this: > 1. Admin adds all necessary Teams, which are essence of the LDAP Groups. > 2. Each Team should be set with default ACL. In this case admin user does > not need to set ACL individually for each User it is set for the whole Team. > 3. Admin associates each Environment with the appropriate set of these > Groups. > > Then only thing admin does is to manage Users in LDAP. When new user is > created admin will give him an appropriate set of the LDAP Groups in the > Active Directory. > > On Saturday, January 16, 2016 at 12:27:04 AM UTC+3, Jay Farschman wrote: >> >> Afternoon, >> >> I setup LDAP access against our MS Active Directory (AD) today and found >> that once you understand how all the parts work, it's really very well >> done. However, I have a question about the workflow >> >> Scalr does not allow me to do any operations on an LDAP user until that >> user first logs in. After they login, I can assign them to teams and apply >> the proper ACLs, but not before then. >> >> How have others handled this? For now I'm personally inviting a limited >> number of users and I can work with them all personally, but if there a >> better, more automated way? >> > -- 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.
