AW: Big hierarchical ZMS-Site with LDAP
Jürgen Klein <[email protected]>
| Newsgroups | gmane.comp.cms.zms.devel |
|---|---|
| Message-ID | <001901c8bb34$df9de6a0$9ed9b3e0$@com> |
hi, couldn't you build your site as multi-site with a zms master-client-configuration in which the zms-master is exclusively used for configuration? Thus, one LDAPUserfolder in zms-master instance should be enough to configure all roles for the clients. regrads jk -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Peter Zechmeister Gesendet: Mittwoch, 21. Mai 2008 09:33 An: ZMS-Developers Betreff: [english 91%] [zms-developers] Big hierarchical ZMS-Site with LDAP Hi ZMS-Developers, we are building a big Site with a structure of hierarchicaly dependent ZMS-Nodes. The main public navigation should get implemented predominant within the topmost ZMS-Node and should gain content by emedding links from the subnodes. We have a lot of different groups with different sights. I guess a lot more than 200 roles (Subscribers, Editors, a lot of different organisational units of our university, ...). Authentication is provided by LDAP. Please can you tell me, where I should place the LDAPUserfolder? I think there are two ways: a) Within the topmost ZMS-Node, with the effect of hundreds of Roles at one single Location and all pros and cons. b) LDAPUserfolder on each ZMS-Node and placing Roles where they affect. But I think there would be some drawbacks concerning hierarchical structure issues, am I right? What would you recommend? Regards PeterZ, JK-University of Linz, Austria -- Die Fabrik der Zukunft wird nur zwei Angestellte haben: einen Mann und einen Hund. Der Mann ist daf�r da, den Hund zu f�ttern. Der Hund ist daf�r da, den Mann daran zu hindern, den Computer zu ber�hren. W. G. Bennis ------------------------------------ Yahoo! Groups Links