I think connection associated to groups, not only to users. Assign permissions to groups too. And permit users to administer a subset of another users (change password, create users, kill active connections, etc). Fine grained permissions, like users can create, but can´t delete users, can´t create connections, can kill connections or not. It will be very, very, good.
And a translatation to portuguese brazilian too. Thanks a lot for our efforts. Aude et Effice! -----Mensagem original----- De: Mike Jumper [mailto:[email protected]] Enviada em: terça-feira, 14 de fevereiro de 2017 02:13 Para: [email protected] Assunto: Re: [DISCUSS] Scope of 0.9.12-incubating On Sat, Feb 11, 2017 at 11:25 PM, Mike Jumper <[email protected]> wrote: > On Fri, Feb 10, 2017 at 11:32 AM, Mike Jumper > <[email protected]> > wrote: > >> ... >> > > The "staging/0.9.12-incubating" branches have now been created for > incubator-guacamole-client, incubator-guacamole-server, and > incubator-guacamole-manual: > > https://git1-us-west.apache.org/repos/asf?p=incubator- > guacamole-client.git;a=shortlog;h=refs/heads/staging/0.9.12-incubating > https://git1-us-west.apache.org/repos/asf?p=incubator- > guacamole-server.git;a=shortlog;h=refs/heads/staging/0.9.12-incubating > https://git1-us-west.apache.org/repos/asf?p=incubator- > guacamole-manual.git;a=shortlog;h=refs/heads/staging/0.9.12-incubating > > Unfortunately, the branches haven't yet shown up in the GitHub > mirrors, and incubator-guacamole-server has yet to reflect the past > deletion of "staging/0.9.11-incubating". If the branches don't appear > on their own in the next day or so, I'll ping Infra... based on past > issues with the automated sync to GitHub [1] [2] [3], I would bet a manual > resync is needed. > > - Mike > > [1] https://issues.apache.org/jira/browse/INFRA-12699 > [2] https://issues.apache.org/jira/browse/INFRA-13229 > [3] https://issues.apache.org/jira/browse/INFRA-13293 > > Issue opened with Infra: https://issues.apache.org/jira/browse/INFRA-13513
