Le ven 03/10/2003 à 15:25, Buchan Milne a écrit : > FACORAT Fabrice wrote:
> And, before deciding on an implementation concept, we would need to list > requirements (and from a Mechanical Design procedure point of view, the > weigthing on requirements, engineering requirements, engineering > specifications). indeed. but it's just idea. > For instance, you might want to ensure that even if a machine in a group > is not accessible when you make the change, that the change should be > applied to the machine as soon as it is able to apply the change. good point > Also, if you are going to be applying changes like this, they should > also be tied to an authentication database. You may also want to cover > the interaction of users in the configuration. > > Although this is premature from a design procedure point of view, my > concept would be to store the configuration in LDAP. Configurations > could be grouped by OU. User settings could be stored in LDAP (or at > least the defaults for a group). LDAP also gives you authentication, TLS > support, dedundancy, rights management (allow a non-root user to set > default settings for a certain group of machines or users). > > In effect, we need something as capable as Netware's NDS/eDirectory or > MS AD. see my next upcoming mail ;)
