More authentication issues with bulkloader.py

[Cynthia Kurtz]

Hi, I've been following the threads having to do with the --dump and --
restore options for the bulk loader. This is a functionality I'd
really like to use for backup/restore. It is a welcome tool and I hope
it can be kept and improved. (That is, if I can get it to work!!)

I am using Google Apps to connect a URL to my app (http://
rakontu.net). As recommended, I've added a second administrator to the
app with a gmail account that is NOT connected to the Google Apps
account. I am trying to give that email to bulkupload.py.

However, I still get the same "Authentication failed" error as I did
with the Google-Apps-connected account:

[ERROR ] Exception during authentication
Traceback (most recent call last):
...
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
HTTPError: HTTP Error 404: Not Found
[INFO ] Authentication Failed

Some people seem to say that using the other gmail account should
work, but others seem to have encountered the same problem I have even
after they followed the instructions and set up a separate account.

Here is the command I'm trying (separating out the parameters to make
it easier to read):

python /usr/local/bin/bulkloader.py
--dump
--url=http://rakontu.appspot.com/remote-api
--kind=Rakontu
--filename=rakontu_dump.txt
--app_id=rakontu

I've tried it with and without each of these parameters:

--email=<account>@gmail.com
--auth_domain=gmail.com
--passin

and it makes no difference. It never asks for a password and it always
gives the same error. I've tried every possible combination of URLs
and app_id. I've got the remote_api first in app.yaml. I've tried
running appcfg update before I run bulkloader.py. The account I'm
trying to use to run bulkloader.py is definitely not connected to a
Google Apps domain and definitely not the same one as I'm using with
appcfg.

What else is there to try?

Cynthia Kurtz

[Nick Johnson (Google)]

Hi Cynthia,

What is your App ID? Are you positive you've accepted the invitation on the correct (gmail) account? Also, can you please paste your app.yaml?

-Nick Johnson

--
Nick Johnson, Developer Programs Engineer, App Engine
Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047

[Elias Torres]

This might be a stupid question, but did you enable remote_api via
app.yaml?

- url: /remote_api
script: $PYTHON_LIB/google/appengine/ext/remote_api/handler.py
login: admin

Best,

-Elias

[Cynthia Kurtz]

The App ID is rakontu. Yes, I've accepted the invitation on the other
account. Both accounts show in the Developers screen on the GAE
Dashboard.

==================================== app.yaml
application: rakontu
version: alpha-0-9-2
runtime: python
api_version: 1

default_expiration: "4d"

handlers:

- url: /remote_api
script: $PYTHON_LIB/google/appengine/ext/remote_api/handler.py
login: admin

- url: /favicon.ico
static_files: images/favicon.ico
upload: images/favicon.ico

- url: /images
static_dir: images

- url: /stylesheets
static_dir: stylesheets

- url: /javascript
static_dir: javascript

- url: /.*
script: main.py
====================================

Thanks for your help!

Cynthia Kurtz

[Cynthia Kurtz]

Yep. Right at the top too. Thanks for asking.

[Nick Johnson (Google)]

Hi Cynthia,

The URL is 'remote_api' (note the underscore), but the URL you're passing to the bulk loader is "remote-api".

-Nick Johnson

[Cynthia Kurtz]

That fixed it. Thanks.

May I respectfuly submit that the error reporting in bulkloader is not
all it could be? One would not think that mistyping a URL would lead
to a report of an authentication error. In fact I think the "bad URL"
thought fleetingly occurred to me, but it didn't have time to settle
before the "Authentication failed" message led me back to thinking it
was an account error. If it had said "URL not found" I could have
fixed it in 30 seconds. Perhaps more fine-grained error reporting
would help others avoid this issue.

But having said that thanks for your help ;)

Cynthia Kurtz

On Sep 25, 8:42 am, "Nick Johnson (Google)" <nick.john...@google.com>
wrote:

[Nick Johnson (Google)]

Hi Cynthia,

On Sun, Sep 27, 2009 at 12:26 AM, Cynthia Kurtz <cfk...@cfkurtz.com> wrote:

That fixed it. Thanks.

May I respectfuly submit that the error reporting in bulkloader is not
all it could be? One would not think that mistyping a URL would lead
to a report of an authentication error. In fact I think the "bad URL"
thought fleetingly occurred to me, but it didn't have time to settle
before the "Authentication failed" message led me back to thinking it
was an account error. If it had said "URL not found" I could have
fixed it in 30 seconds. Perhaps more fine-grained error reporting
would help others avoid this issue.

The line immediately before 'authentication failed' was "HTTPError: HTTP Error 404: Not Found". I agree that we could make this clearer by removing authentication from the equation, though.

-Nick Johnson