On Mon, Nov 14, 2005 at 01:35:30PM +0100, Dario Lopez-Kästen wrote:
| Sidnei da Silva wrote:
| caveat, I am not into PAS yet, I am only following the discussion for
| fuutre work, so I may not be understanding corretly how PAS works:
| "first found above" sounds like it is the Zope-root in a normal Plone
| install: ie. / is the zope root, where there is an acl_users. /Portal is
| the Plone default install. /Portal/acl_users is the non-pas location of
| a user folder if one creates one at or after creating a Plone Site object.
| "first found above" means... /Portal/../acl_users --> /acl_users?
| Or does "first found above" mean /Portal/acl_users ?
| Assuming, I have understood this correclty, if there is no
| /Portal/acl_users, then I can understand that there logically is no
| other user folder than /acl_users to PAS-ify... but that is, imho,
| perhaps a bit too invasive - better to offer the user an option to
| create a new PAS-ified acl_users at /Portal level rather than silenlty
| PAS-ify the root acl_users.
It will always PAS-ify the nearest (*usually* root) acl_users if and
only if it's a standard user folder.
If /Portal/acl_users does not exist, a PAS will be created there
setup to support cookie authentication.
| We have all learned that replacing the root acl_users is generally not a
| good idea, so doing this semi-silently is perhaps a bit premature. Until
| Zope ships with PAS as the default user folder implementation, replacing
| root user folders should be treated as a special case that is to be
| avoided and alternative options should be offered.
| Apologies if I am misunderstanding everything and wasting bandwith.
My opinion is that PAS is mature enough to serve as a replacement of a
standard user folder, which is what we are using it as.
This is getting too PlonePAS specific, better ask those questions in
Sidnei da Silva
Enfold Systems, LLC.
Zope-PAS mailing list