why is that code no longer referring to the real userfolder anymore? it
should not make calls to authorize/identify/authorize on self but on
the LDAPUserFolder it is using as the user source.
jens
On Thursday, Oct 17, 2002, at 03:39 US/Eastern, Dirk Datzert wrote:
Hi all,
I try to solve
Hi Jens,
why is that code no longer referring to the real userfolder anymore? it
should not make calls to authorize/identify/authorize on self but on
the LDAPUserFolder it is using as the user source.
self.identify() should be the same as if getLUF().identify() since LDAPUserFolder and
being explicit is almost always better. you are relying on internal
magic and it's not apparent from looking at the code you wrote.
the validate implementation in the LDAPRoleExtender is the most
correct one. shane worked on it for a while to make sure it does the
most correct thing possible,
Jens Vagelpohl wrote:
being explicit is almost always better. you are relying on internal
magic and it's not apparent from looking at the code you wrote.
the validate implementation in the LDAPRoleExtender is the most
correct one. shane worked on it for a while to make sure it does the
most
Hi Shane,
thanks for answering.
Maybe I'm think too complicated, Your opinion ?
The idea behind LDAPRoleExtender is to give the user global roles if the
I don't know anything about LDAPRoleTwiddler. But I would recommend you
install the VerboseSecurity product, which will tell you a
if I access /dir2/index_html comes the user object from LRT2 ?
what if I access in /dir2/index_html aq_parent.dir1.index_html.
Will the AUTHENTICATED_USER change ? will the user object come from LRT2
?
No, it will not. Only one user ever applies to a request.
And that exactly what
