> On the other side if there is no AD support this will just enforce admins to > duplicate some information which is supposed to be quite static. So the > drawbacks seem not to be a no-go criteria to me. > > However with an architectural change I would like to achieve certain > decoupling > between XML-based configuration and AD-based configuration so impacts should > be > smaller. > > > Perhaps there is workaround by using some tool to dump security membership > > content to the profile-host XML files. Therefore, such tool/script might > > run periodically to upate WPKG XML files to reflect current AD security > > group memberships. > > Another negative side effect of integrating AD connectivity in wpkg.js is just > the code overhead. Currently wpkg.js is already ~200kB in Size which has to be > fetched by WSH and run within the interpreter. Adding AD/LDAP support might > easily add another 40kB of code. > > > Sorry for the longish explanation, I was just in the mood to summarize the > topic > again since it pops up from time to time. So in the future I can refer to this > message where my main concerns are already written down.
These arguments are very well reasoned. I agree with your POV. In such case, I will setup some synchro between groups membership and XML files. Thanks for your time and effort, it is appreciated! Regards, Andrew ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
