|
Author
|
Message
|
|
ANCA GROZEA
|
Tuesday 30 September 2008 3:34:06 pm
Hello,
I am thinking about building an eZ Publish site and I wonder where should I store my users if in /Users or in /Content if:
- My users need to authenticate via AD / LDAP
- I need to create an employee directory where for each user I will have to display several info such as name, contact info (email, tel etc), job description, manager, team he is part of, keywords, list of blogs, recent comments on blog/forum.
- users will have various types of access depending on their groups membership. Please advice,
Thank you!
Anca
|
|
Ivo Lukac
|
Wednesday 01 October 2008 1:54:50 am
Hello Anca, I had similar dilemma on one project and I can suggest to leave your users in /Users part. To make this happen you need to give read access to part of the /Users tree where your users are and map this part to web within templates.
http://www.linkedin.com/in/ivolukac
http://www.netgen.hr/eng/blog
http://twitter.com/ilukac
|
|
Mark Marsiglio
|
Wednesday 01 October 2008 6:40:07 am
We have done it like Ivo suggested in a few cases, and sometimes we set up a workflow to (or manually) create an additional location for the user account within the content tree.
http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions
|
|
Paul Borgermans
|
Wednesday 01 October 2008 7:27:08 am
Hi Anca :-) No worries to extend the user class with attributes you need Authentication can be done independently of the attributes (or do these also need to come from the AD? hopefully not)
Cheers
Paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
André R.
|
Wednesday 01 October 2008 12:35:43 pm
How many users are we talking about?
If your planning on going up in the 100.000 ranges, then you should try to keep attributes and user object versions low.
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|
|
Paul Borgermans
|
Wednesday 01 October 2008 2:14:38 pm
In this case, there are not that many users .. but indeed, many attributes x many users x many versions can inflate some tables beyond usable limits (performance, maintenance) wise Paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
|
John Moritz
|
Thursday 02 October 2008 1:01:26 am
in this case... what is too much? I have a community with not that many users > 10.000 but many pictures. There are about 230.000 Pictures (growing: 1000 Pictures more per week). At the moment i am thinking about to integrate all into ezPublish but i am not sure. Now i think its better to leave it external...? I was also asking about using of LDAP in a previous Thread. Because i have no experience with LDAP and i want to migrate my existing users to ez, i am not sure if its a good idea to use LDAP for authentication. On one side it will help me to connect different systems like ezpublish and a jabber server or a external forum which also has available LDAP auth. But how is speed when compare mysql and LDAP on growing Users, < 100.000? Is LDAP a good auth method for ez or more experimental? Is LDAP good for Web-Communitys or just for Intranet use with not that many Users?
|
|
Mickael Robin
|
Monday 06 October 2008 1:10:04 am
@ Mark : Could you please explain how you set up a <b>workflow to automatically add a location</b> in the content tree (i.e Content section) to a user object created in the Users section ?
Thanks in advance,
Mickael.
|
|
ANCA GROZEA
|
Wednesday 08 October 2008 2:23:40 am
Hello everyone, Thank you for your replies.
@André R: there will be no more than 300-500 users.. nothing compared to 10.000 but a lot to set up manually..
@Paul Borgermans: Hi Paul! :)
Initially i will load the users from AD (name, user id, email, department it, maybe also manager id). In the site users have to log in to contribute or to access restricted areas and logging in should be made through AD. The extra attributes i need will be used to for Employee's Directory - job name, description, photo.. etc So far I understood that I have to create users in /Users and can make that content available via templates. Any suggestions about ways to import the users?
Have a nice day!
Anca
|
