I don't think so. The PAU is quite a big chunk and would really
deserve to live on its own piece of land.
zope.authentication is really about the authentication basics, not all
the pluggability and plugin that PAU brings in.
zope.app.authentication is just too confuse as it defines PAU and a
whole set of persistent authentication-relatied components and other
things that could be easily (logically) cut off.

2010/1/22 Hanno Schlichting <ha...@hannosch.eu>:
> On Fri, Jan 22, 2010 at 7:59 PM, Souheil CHELFOUH <troll...@gmail.com> wrote:
>> I'm coding some stuff, using zope.app.authentication and this package
>> appears to do too many things, in my opinion.
>> Would it be wise to cut off some of the functionalities ? The pure PAU
>> components could go in a dedicated package, like
>> zope.pluggableauthservice
> I don't have a good understanding of any of the security related
> features of Zope 3, but it looks like we already have a lot of
> packages. Would it make sense to put it into any of the existing ones?
> There's at least:
> zope.authentication
> zope.login
> zope.password
> zope.principalannotation
> zope.principalregistry
> zope.security
> zope.securitypolicy
> Hanno
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to