Re: [Zope3-Users] pluggable authentication utility
On Saturday 18 June 2005 13:36, Garrett Smith wrote: > > For 3.2, we need to find a way to make this clearer. Either we need > > to provide a more verbose description of what the name is for or > > perhaps, as Stephan has suggested, for components that are always > > looked up without names, we should not provide the option of entering > > a name and, for others, we should require a name. > > IMO, the PAU pattern of not taking a name works well. The confusion > above may be a hold-over from the time when PAU regs did accept names. Right. In my opinion all nameless utilities are what services used to be. I have not yet seen an exception to this rule. The terminology I introduced for them in the new Tools UI (now called Site Management) is "Unique Utilities", since they are unique to a given site. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
RE: [Zope3-Users] pluggable authentication utility
Jim Fulton wrote: > Roger Ineichen wrote: >> Hi Ricki >> >> On Behalf Of GMane >> >>> Sent: Wednesday, June 15, 2005 5:52 PM >>> To: zope3-users@zope.org >>> Subject: [Zope3-Users] pluggable authentication utility >>> >>> Hi, >>> I have a simple question about pluggable authentication. >>> >>> I created a folder and I made it a site. >>> In the default Site-Management Folder I created a Pluggable >>> Authentication Utility (named plaut). >>> Inside it I made a PrincipalFolder (Partner) and added a user soc1. >> >> >> Don't give a name (plau). Pluggable authentication utilities >> are as dfault unnamed. All components right now will lookup the >> PAU with name=''. The PAU registration doesn't accept a name. He's likely talking about the PAU's name itself, which can be anything. > For 3.2, we need to find a way to make this clearer. Either we need > to provide a more verbose description of what the name is for or > perhaps, as Stephan has suggested, for components that are always > looked up without names, we should not provide the option of entering > a name and, for others, we should require a name. IMO, the PAU pattern of not taking a name works well. The confusion above may be a hold-over from the time when PAU regs did accept names. -- Garrett ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] pluggable authentication utility
Roger Ineichen wrote: Hi Ricki On Behalf Of GMane Sent: Wednesday, June 15, 2005 5:52 PM To: zope3-users@zope.org Subject: [Zope3-Users] pluggable authentication utility Hi, I have a simple question about pluggable authentication. I created a folder and I made it a site. In the default Site-Management Folder I created a Pluggable Authentication Utility (named plaut). Inside it I made a PrincipalFolder (Partner) and added a user soc1. Don't give a name (plau). Pluggable authentication utilities are as dfault unnamed. All components right now will lookup the PAU with name=''. For 3.2, we need to find a way to make this clearer. Either we need to provide a more verbose description of what the name is for or perhaps, as Stephan has suggested, for components that are always looked up without names, we should not provide the option of entering a name and, for others, we should require a name. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
RE: [Zope3-Users] pluggable authentication utility
Hi Ricki On Behalf Of GMane > Sent: Wednesday, June 15, 2005 5:52 PM > To: zope3-users@zope.org > Subject: [Zope3-Users] pluggable authentication utility > > Hi, > I have a simple question about pluggable authentication. > > I created a folder and I made it a site. > In the default Site-Management Folder I created a Pluggable > Authentication > Utility (named plaut). > Inside it I made a PrincipalFolder (Partner) and added a user soc1. Don't give a name (plau). Pluggable authentication utilities are as dfault unnamed. All components right now will lookup the PAU with name=''. > Every credential plugin is active > > When I try to connect via ftp on localhost:9021 with the soc1 > user I can > list all the folders but not the ++etc++site. > (I can do it with a user (manager) I've added in the principals.zcml) > > the error message is: > Unauthorized: ( 0x9134aac>, '__iter__', 'zope.ManageSite') > > What should I do? > I am a total newbie. > Thanks > > Ricki Regards Roger Ineichen Projekt01 GmbH www.projekt01.ch _ END OF MESSAGE ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
