Next OSS release will contain this fix. We're expecting release within the next couple weeks.
On 15 May 2015 at 08:26, Matt Shibla <[email protected]> wrote: > I am running Scalr OSS 5.3.2, revision a449979. Glad to hear this is a > solved problem. Thanks for the info. > > > On Friday, May 15, 2015 at 11:12:06 AM UTC-4, Matt Shibla wrote: >> >> We are running a beta test of Scalr with some of our users. We currently >> have 9 AD groups defined to provide access to 6 different environments. 7 >> of the 9 teams have default ACL's set correctly. 2 of them seem to be set >> correctly when hitting the save button, but when navigating away and then >> back to the team, Scalr shows no Default ACL. Additionally, when I set >> individual user ACL's on that page, I get the same behavior (appears to >> save, but when navigating away and back, the ACL isn't shown--it displays >> "No access" in red). >> >> This unexpected behavior happens in the 2 teams which have periods (".") >> in their name. Is this failure to store ACL's possibly related to the >> spelling of the "Team" name (i.e. the AD group name)? > > -- > 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.
