Hi,
Does anybody know what is the method call to modify the AUTHENTICATED_USER attribute?
I am unable to trace where REQUEST feeds data for its AUTHENTICATED_USER attribute.
Some context to my question: I am using a custom method to authenticate users coming
to my site. So when the user logs in
the user gets modified automatically, provided you use common
login-methodology and a user folder that supports it.
you don't set the user "manually".
jens
On Monday, January 21, 2002, at 12:35 , vio wrote:
> Hi,
> Does anybody know what is the method call to modify the
> AUTHENTICATED_USER
The point in a customised login method is precisely to do just that: validate
user credentials with some custom scheme. If interested, this is trivial to do
with a valid UserFolder instance around:
'if my_custon_loginForm_password ==
Users_folder.getUser(my_custon_loginForm_loginName)._getPass
the user folder does this "switch". it's not something you should do
manually.
by the way, since replying to your previous email to me bounced back
("[EMAIL PROTECTED]" is unknown) i'm uncluding that here:
**
vio,
i'm not sure what user folder products you were looking at, the
Co
Hi Vio,
By the contents of your message, you seem to be a little off track
w.r.t. the way authentication works between the browser and Zope.
By now you seem to have discovered that the browser sends the user
credentials whenever it fetches a page. If you aren't using a custom
user folder that us
First, thanks for your time on this thread, everybody!
* Leonardo Rochael Almeida <[EMAIL PROTECTED]> [020123 19:42]:
> Hi Vio,
>
> By the contents of your message, you seem to be a little off track
> w.r.t. the way authentication works between the browser and Zope.
>
> By now you seem to have
Hi vio,
Pardon our insistence in helping you out, but you asked to be told if
something in your description smelt rotten and, besides the fact that
yes, you are reinventing the wheel (and reinventing it square, by the
way :-), there isn't a single thing in the scenario you described below
that is
All the user folders can be confusing, but I think in the long run,
you'd be better off if you grabbed one and figured out how it worked.
I've used LoginManager, and basically, I create a folder for my project,
don't put the standard acl_users in it, because you want to create an
object called
* Leonardo Rochael Almeida <[EMAIL PROTECTED]> [020124 00:03]:
> Hi vio,
>
> Pardon our insistence in helping you out, but you asked to be told if
> something in your description smelt rotten and, besides the fact that
> yes, you are reinventing the wheel (and reinventing it square, by the
> way
vio,
for your situation the simplest thing would be to use the CookieUserFolder
(see http://www.dataflake.org/software/cookieuserfolder) which is as
simple as the standard user folder and adds cookie-capability and
customizable login and logout forms.
no need to get all tripped up in zpattern
Excellent! Precisely what I'm looking for. Thanks!
Vio
* Jens Vagelpohl <[EMAIL PROTECTED]> [020124 10:46]:
> vio,
>
> for your situation the simplest thing would be to use the CookieUserFolder
> (see http://www.dataflake.org/software/cookieuserfolder) which is as
> simple as the standard user
vio,
make sure you read the README so you don't lock youself out if the login
form does not have the correct input fields.
jens
On Thursday, January 24, 2002, at 10:55 , vio wrote:
> Excellent! Precisely what I'm looking for. Thanks!
> Vio
>
> * Jens Vagelpohl <[EMAIL PROTECTED]> [020124 10:
--On Thursday, January 24, 2002 01:35:56 AM -0500 vio
<[EMAIL PROTECTED]> wrote:
> exUserFolder installed ok, so I'll give it a test drive also.
> But some hints on debugging LoginMgr would be also appreciated.
Personally, I'd stay away from LoginManager. It depends on ZPatterns,
a very impr
13 matches
Mail list logo