upload.py

[fUD]

Hi Guys,

I was having a hack around to get rietveld authentication going with
LDAP as we have an ldap server, rather than authenticating with
google. But I've been unable to work out how gae2django is emulating a
call to /_ah/login. Specifically I've been looking at,


def _GetAuthCookie(self, auth_token):
...
continue_location = "http://localhost/"
args = {"continue": continue_location, "auth": auth_token}
req = self._CreateRequest("%s/_ah/login?%s" %
(self.host, urllib.urlencode(args)))
try:
response = self.opener.open(req)
...

It does a connection to the django server requesting /_ah/login but
URLs.py has no /_ah/login from what I can see?

Thanks,
Brent.

[Andi Albrecht]

Hi Brenton,

On Tue, Jun 14, 2011 at 12:33 PM, fUD <fud...@gmail.com> wrote:
> Hi Guys,
>
> I was having a hack around to get rietveld authentication going with
> LDAP as we have an ldap server, rather than authenticating with
> google. But I've been unable to work out how gae2django is emulating a
> call to /_ah/login. Specifically I've been looking at,

there's no need to hook into /_ah/login. The authentication flow that
the gae2django version of upload.py uses is slightly different and
talks with the default authentication mechanism that Django provides.
This means that you can simple add an Django authentication backend
that talks to you LDAP.

Let me know, if you need further information. We have such a setup
running at work too.

Best regards,

Andi