On Fri, Jul 18, 2008 at 05:00:50PM +0200, Hermann Himmelbauer wrote:
Am Freitag, 18. Juli 2008 03:55 schrieb Florian Friesdorf:
(..)
In case you store your userdata in RDB, you do not need InternalPrincipal
at all. I currently see to options:
1. custom AuthenticatorPlugin,
Am Freitag, 18. Juli 2008 03:55 schrieb Florian Friesdorf:
On Wed, Jul 16, 2008 at 10:20:58AM +0200, Hermann Himmelbauer wrote:
Am Mittwoch, 16. Juli 2008 05:48 schrieb Florian Friesdorf:
InternalPrincipal is a persistent object used to store the data of
principals in a PrincipalFolder,
On Wed, Jul 16, 2008 at 10:20:58AM +0200, Hermann Himmelbauer wrote:
Am Mittwoch, 16. Juli 2008 05:48 schrieb Florian Friesdorf:
InternalPrincipal is a persistent object used to store the data of
principals in a PrincipalFolder, PrincipalInfo is returned upon successfull
authentication and
Am Mittwoch, 16. Juli 2008 05:48 schrieb Florian Friesdorf:
On Mon, Jul 14, 2008 at 09:50:25AM +0200, Hermann Himmelbauer wrote:
(..)
1) No way to pass PAU-related information to form-code: In PAU, the
(..)
2) Lack of documentation: The entities Principal, InternalPrincipal,
Tres Seaver wrote:
Mark Hammond wrote:
Well, Zope moved onwards from PAS to PAU
I doubt that seriously: I would venture that there are two orders of
magnitude more users of PAS than PAU in production deployments. PAU was
an attempt to port the PAS to a component-centric implementation, but
On Mon, Jul 14, 2008 at 09:50:25AM +0200, Hermann Himmelbauer wrote:
(..)
1) No way to pass PAU-related information to form-code: In PAU, the
(..)
As I using PAU within Plone and PlonePAS to handle the credential extraction and
form stuff, I can't say anything about PAU's capabilities of
On Sat, Jul 12, 2008 at 02:04:32PM +0100, Martin Aspeli wrote:
I think it's worth displaying some sensitivity to the context of Google
Summer of Code here. I too worry that PAULA may throw the baby (PAS) out
with the bathwater.
However, GSoC is an excellent incubator of RD, and has
Am Samstag, 12. Juli 2008 03:04 schrieb Florian Friesdorf:
On Thu, Jul 10, 2008 at 10:56:19PM +0200, Wichert Akkerman wrote:
Previously Florian Friesdorf wrote:
Hi *,
PAS works fine and covers a lot more functionality than PAU and there are
more PAS plugins than PAU plugins.
PAU is
Martin quoting me:
I was referring to the thread at
http://mail.zope.org/pipermail/zope-pas/2004-September/86.html,
entitled [Zope-PAS] Challengers (and Zope 3)
...
Sorry, I may've gotten my history mixed up a little here, but in any
case, I think the point remains: no-one's said
Previously Mark Hammond wrote:
Martin quoting me:
I was referring to the thread at
http://mail.zope.org/pipermail/zope-pas/2004-September/86.html,
entitled [Zope-PAS] Challengers (and Zope 3)
...
Sorry, I may've gotten my history mixed up a little here, but in any
case, I
Zope3 has never supported PAS and I doubt it ever well.
That is a shame - the thread I referred to shows that Jim was working on
exactly that - it's a shame that never came to fruition (and indeed, its not
clear why that attempt failed - should PAS have been fixed to make that
transition
--On 13. Juli 2008 19:38:01 +0300 Mark Hammond [EMAIL PROTECTED]
wrote:
Since Zope3 is not a successor to Zope2 but a
completely different thing I do not think this is problematic.
That too seems a shame to me. So if I found myself with an investment in
Zope2 but was looking to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Hammond wrote:
Zope3 has never supported PAS and I doubt it ever well.
That is a shame - the thread I referred to shows that Jim was working on
exactly that - it's a shame that never came to fruition (and indeed, its not
clear why that
Well, Zope moved onwards from PAS to PAU and I think Plone should too,
because:
It seems like just yesterday that PAS offered the promise of being the nice
clean way forward for authentication, and even offered a path to Zope3.
I've been subscribed to zope-dev since then, but somehow the
--On 11. Juli 2008 18:04:16 -0700 Florian Friesdorf [EMAIL PROTECTED]
wrote:
On Thu, Jul 10, 2008 at 10:56:19PM +0200, Wichert Akkerman wrote:
Previously Florian Friesdorf wrote:
Hi *,
within the scope of google summer of code I am integrating zope 3's
PAU with Plone's PAS and further
On Jul 12, 2008, at 09:33 , Mark Hammond wrote:
Well, Zope moved onwards from PAS to PAU and I think Plone should
too,
because:
It seems like just yesterday that PAS offered the promise of being
the nice
clean way forward for authentication, and even offered a path to
Zope3.
I've been
On Jul 12, 2008, at 03:04 , Florian Friesdorf wrote:
On Thu, Jul 10, 2008 at 10:56:19PM +0200, Wichert Akkerman wrote:
The one thing I am missing is: why?
Well, Zope moved onwards from PAS to PAU
Huh? Zope 2 uses PAS. The Zope 3 folks have attempted to come up with
a similar solution,
Mark Hammond wrote:
Well, Zope moved onwards from PAS to PAU and I think Plone should too,
because:
It seems like just yesterday that PAS offered the promise of being the nice
clean way forward for authentication, and even offered a path to Zope3.
I've been subscribed to zope-dev since then,
Jens Vagelpohl wrote:
I call BS here. PAS is not a custom solution, it's much more of a
standard than PAU is.
The question remains, why?. You're reinventing wheels for Zope 2
that do not need to be reinvented. One day when PAU has indeed
surpassed PAS in terms of functionality and
may or may become a part of Zope and/or Plone in the future. Well
put Martin. ;)
--
Sidnei da Silva
Enfold Systems http://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
___
Zope-Dev maillist - Zope-Dev@zope.org
Sidnei da Silva wrote:
may or may become a part of Zope and/or Plone in the future. Well
put Martin. ;)
Hah, obviously I meant may or may not. :)
Martin
--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Hammond wrote:
Well, Zope moved onwards from PAS to PAU
I doubt that seriously: I would venture that there are two orders of
magnitude more users of PAS than PAU in production deployments. PAU was
an attempt to port the PAS to a
I think you've misunderstood slightly here ... PAS was and is a Zope 2
user folder implementation. It pre-dates Zope 3 (at least as we know it
now).
I was referring to the thread at
http://mail.zope.org/pipermail/zope-pas/2004-September/86.html, entitled
[Zope-PAS] Challengers (and Zope 3)
Mark Hammond wrote:
I think you've misunderstood slightly here ... PAS was and is a Zope 2
user folder implementation. It pre-dates Zope 3 (at least as we know it
now).
I was referring to the thread at
http://mail.zope.org/pipermail/zope-pas/2004-September/86.html, entitled
[Zope-PAS]
On Thu, Jul 10, 2008 at 10:56:19PM +0200, Wichert Akkerman wrote:
Previously Florian Friesdorf wrote:
Hi *,
within the scope of google summer of code I am integrating zope 3's PAU with
Plone's PAS and further enable (non-AT) content objects as source for users
and
groups. All
On Thu, Jul 10, 2008 at 05:01:49PM -0400, Philipp von Weitershausen wrote:
Wichert Akkerman wrote:
Previously Florian Friesdorf wrote:
Hi *,
within the scope of google summer of code I am integrating zope 3's PAU
with
Plone's PAS and further enable (non-AT) content objects as source
Previously Florian Friesdorf wrote:
Hi *,
within the scope of google summer of code I am integrating zope 3's PAU with
Plone's PAS and further enable (non-AT) content objects as source for users
and
groups. All functionality is developed in pure zope3, the plone integration is
happening
Previously Philipp von Weitershausen wrote:
Wichert Akkerman wrote:
Previously Florian Friesdorf wrote:
Hi *,
within the scope of google summer of code I am integrating zope 3's PAU
with
Plone's PAS and further enable (non-AT) content objects as source for
users and
groups. All
Wichert Akkerman wrote:
Previously Florian Friesdorf wrote:
Hi *,
within the scope of google summer of code I am integrating zope 3's PAU with
Plone's PAS and further enable (non-AT) content objects as source for users and
groups. All functionality is developed in pure zope3, the plone
29 matches
Mail list logo