Well. (This answer could also be posted a bit up the thread)
I think we see that Cookie Crumbler may not be the solution to what i
originally itended - the availability of cookie based authentication
in the standard userfolder. Due to its problems, it seems as if it would
be best, to extend the f
ts in turning the devious into
the direct, and misfortune into gain.
- Sun Tzu
- Original Message -
From: "Matt Behrens" <[EMAIL PROTECTED]>
To: "Christian Theune" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, March 05, 2002 8:32 PM
Subjec
Christian Theune wrote:
> Hmm. I didn't get an answer right now (well i don't find the question again too)
> if the cookie crumbler would interfere subfolders (distor through acquisition)
> or would only be active on a "sibling" userfolder, which he is "watching".
I'm really not sure. I imagin
Howdi.
On Tue, Mar 05, 2002 at 09:08:58PM +0100, Dario Lopez-Kästen wrote:
> From: "Matt Behrens" <[EMAIL PROTECTED]>
> > Well, as far as "least-intrusive", CC loses some points by not being
> > compatible with some of the user folders that do their own cookie auth,
> > although that's arguably n
I like the idea of adding cookie auth to the API. The user product choices
are convoluted and I think the community would benefit from adding standard
capability to the core.
Adding to that...
my priority would be to extend acl_users folder to allow for built-in
storage of additional user proper
> Which makes me think of another point. I haven't used Zope 2.5.1 yet, but
I
> understand from some of the traffic on the mailinglists that some have
> wanted to disable the session tracking/session management beause it
> interferes with the solutions they allready use for session tracking.
This
