Comment 4 for bug 589345

Here is an example session:

>> BEGIN EXAMPLE
dsowen@lithium:~$ ./create_app_token.sh "<email address hidden>" "MyP4ssw0rd" "ec2-184-73-98-244.compute-1.amazonaws.com"
--2010-07-19 13:00:03-- http://ec2-184-73-98-244.compute-1.amazonaws.com/api/1.0/authentications?ws.op=authenticate&token_name=test
Resolving ec2-184-73-98-244.compute-1.amazonaws.com... 184.73.98.244
Connecting to ec2-184-73-98-244.compute-1.amazonaws.com|184.73.98.244|:80... connected.
HTTP request sent, awaiting response... 401 Unauthorized
Connecting to ec2-184-73-98-244.compute-1.amazonaws.com|184.73.98.244|:80... connected.
HTTP request sent, awaiting response... 200 Ok
Length: 229 [application/json]
Saving to: `/dev/null'

100%[======================================>] 229 --.-K/s in 0s

2010-07-19 13:00:04 (10.6 MB/s) - `/dev/null' saved [229/229]
>> END EXAMPLE

At this point, the script has succeeded in creating a token. Going to "http://ec2-184-73-98-244.compute-1.amazonaws.com/+applications" displays the token that was created.