[uportal-dev] uP3 template user & default groups
We created a new defaultTemplateUser for the framework to use as a template for all new users. This replaces the demo user that has been used until now. The demo user was in the Developer group which resulted in all new users being placed in that group. Should we simply add the defaultTemplateUser to the same group? A few other ideas are to create an All Users group under Everyone and add the defaultTemplateUser to that or to enable PAGs by default and create an All Users group that will match any user and have that under Everyone. I don't think we can put defaultTemplateUser directly in the Everyone group as there are a few places in the framework that load all direct children of the Everyone group which gets very slow in large installs. -Eric smime.p7s Description: S/MIME Cryptographic Signature
Re: [uportal-dev] uP3 template user & default groups
Eric Dalquist wrote: We created a new defaultTemplateUser for the framework to use as a template for all new users. This replaces the demo user that has been used until now. [...] Sounds great. A few other ideas are to create an All Users group under Everyone and add the defaultTemplateUser to that or to enable PAGs by default and create an All Users group that will match any user and have that under Everyone. I think the PAGS version is the better approach. Scalability issues in the local group store are not limited to the Everyone group; anywhere in the groups tree where many thousands of users are direct members of a database group will become a "tar pit" that's difficult to access with the UI. Channels that use the GroupsManager servant will tend to timeout as you try to pass through there. +1 for PAGS in the default config. drew wills -- Join your friends and colleagues at JA-SIG 2008 - "Higher Education Solutions: The Community Source Way!" April 27th - 30th, 2008 in St. Paul, Minnesota USA Featuring CAS, DSpace, Fedora, Fluid, Internet2, Kuali, Sakai, uPortal, and more! Information/Registration at: http://www.ja-sig.org/conferences/08spring/index.html Subscribe to the conference blog, The Community Source Way http://jasig2008.blogspot.com, for news and updates about the event. Join the Conference networking site at http://ja-sigspring08.crowdvine.com/ You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
Re: [uportal-dev] uP3 template user & default groups
I think I'm confused by what you said here. You said you changed defaultTemplateUser and gave one of the reasons why, because you didn't think that all users should be added to the developer group. Then you ask if we should put the new template user in the developer group. What am I missing? Cris J H Eric Dalquist wrote: We created a new defaultTemplateUser for the framework to use as a template for all new users. This replaces the demo user that has been used until now. The demo user was in the Developer group which resulted in all new users being placed in that group. Should we simply add the defaultTemplateUser to the same group? -- Join your friends and colleagues at JA-SIG 2008 - "Higher Education Solutions: The Community Source Way!" April 27th - 30th, 2008 in St. Paul, Minnesota USA Featuring CAS, DSpace, Fedora, Fluid, Internet2, Kuali, Sakai, uPortal, and more! Information/Registration at: http://www.ja-sig.org/conferences/08spring/index.html Subscribe to the conference blog, The Community Source Way http://jasig2008.blogspot.com, for news and updates about the event. Join the Conference networking site at http://ja-sigspring08.crowdvine.com/ You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
Re: [uportal-dev] uP3 template user & default groups
Ok, in that case, I do not think that everyone in a uPortal deployment should be in the Developers group. If the developers group is going to exist, it should have some kind of 'developers' meaning, not really be synonymous with 'everyone'. But for what it's worth, I'm not sure, in my vision I see a big difference between administrators and developers, where uPortal is concerned permission wise. I'm with Drew on voting the PAGS route to create a rule that matches everyone. And having that PAGS group be a member of Everyone. Cris J H Eric Dalquist wrote: Sorry, the actual impetus for the change was to have a blank user who's only purpose is to be a template for new uPortal users instead of overloading the demo user like had been done historically. The new template user not being in the Developer group is just part of it being a new, blank, user. This does bring up the issue of how do we make new users appear to be in the Everyone group without loading up the database. -Eric Cris J Holdorph wrote: I think I'm confused by what you said here. You said you changed defaultTemplateUser and gave one of the reasons why, because you didn't think that all users should be added to the developer group. Then you ask if we should put the new template user in the developer group. What am I missing? Cris J H Eric Dalquist wrote: We created a new defaultTemplateUser for the framework to use as a template for all new users. This replaces the demo user that has been used until now. The demo user was in the Developer group which resulted in all new users being placed in that group. Should we simply add the defaultTemplateUser to the same group? -- Join your friends and colleagues at JA-SIG 2008 - "Higher Education Solutions: The Community Source Way!" April 27th - 30th, 2008 in St. Paul, Minnesota USA Featuring CAS, DSpace, Fedora, Fluid, Internet2, Kuali, Sakai, uPortal, and more! Information/Registration at: http://www.ja-sig.org/conferences/08spring/index.html Subscribe to the conference blog, The Community Source Way http://jasig2008.blogspot.com, for news and updates about the event. Join the Conference networking site at http://ja-sigspring08.crowdvine.com/ You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
Re: [uportal-dev] uP3 template user & default groups
Sorry, the actual impetus for the change was to have a blank user who's only purpose is to be a template for new uPortal users instead of overloading the demo user like had been done historically. The new template user not being in the Developer group is just part of it being a new, blank, user. This does bring up the issue of how do we make new users appear to be in the Everyone group without loading up the database. -Eric Cris J Holdorph wrote: I think I'm confused by what you said here. You said you changed defaultTemplateUser and gave one of the reasons why, because you didn't think that all users should be added to the developer group. Then you ask if we should put the new template user in the developer group. What am I missing? Cris J H Eric Dalquist wrote: We created a new defaultTemplateUser for the framework to use as a template for all new users. This replaces the demo user that has been used until now. The demo user was in the Developer group which resulted in all new users being placed in that group. Should we simply add the defaultTemplateUser to the same group? smime.p7s Description: S/MIME Cryptographic Signature
