turbine-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Age Mooy" <am...@home.nl>
Subject RE: Security framework (not only a pull tool), Part 1
Date Wed, 24 Oct 2001 08:05:36 GMT

> The DEPLOYER is the one responsible for the configuration, at deploy time,
> of all the module security, in details:
> a) he creates (e.g. using Flux) all the groups, roles, permissions and users
> that he wants
> b) he configures (by editing the TR file) the level of security necessary to
> perform each task of each module family (as defined by the DEVELOPER): he
> can also define a DEFAULT module security

Is there any reason why step b) can't be integrated into Flux ? Maintaining security in two
different places
doesn't seem an ideal solution to me.


To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org

View raw message