-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2 Feb 2007, at 19:45, Sidnei da Silva wrote:
Now, some might argue that this is an application-specific policy. The fact is that there's no obvious way currently of 'vetoing' a login based on the lack of certain user properties (like the email example above). I would like to change PAS so this is possible to do. Any objections?
Instead of adding yet another plugin type (I think there are too many as it is), shouldn't this be handled by an overridden plugin of one of the standard types, like maybe an overridden properties plugin?
I think this is a very narrowly focused functionality that only very few users may ever need. Providing a more specialized "standard" plugin for a specific customer with that need is what I would do instead.
jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFw4wXRAx5nvEhZLIRApayAJ9v1QNwXjN8hYPjCKNdwpZrrkiQtwCfcpjK KEU1mXyeegxtL2JEiGL5P+k= =YjOU -----END PGP SIGNATURE----- _______________________________________________ Zope-PAS mailing list Zope-PAS@zope.org http://mail.zope.org/mailman/listinfo/zope-pas
