Add API token management UI to web

Note to QA: this will need a test case associated with it when it is complete

On the edit page:

1. Move "tokens" from the form up to the navigation between
   the user's name and the logout button

2. Don't use the word "tokens," instead use "Applications"

On the "tokens" page:

3. Change the heading from "List of tokens" to "Applications
   you use"

4. Change the paragraph below the heading to match the text below

   You have used the applications shown here to access your account. If
   you have stopped using one of these and would like to prevent it from
   being used to access your account, click it's "Delete" button
   below. You can choose to allow an application to have access again if
   you like by opening that application and instructing it to access your
   account. You'll have to provide your username and password before it
   will be granted access.

5. Change the label on the buttons from "Revoke" to "Delete."

6. Have the buttons conform to the new styles. As secondary buttons
   they should be grey, not orange

7. Remove the "Go back" link from the "Applications" page.

Preparation:

 1. Save the attached script to your home directory (or someplace else).
 2. From a terminal, run "chmod +x create_app_token.sh"
 3. Run "./create_app_token.sh" You should receive a short usage message.

Example use:

./create_app_token.sh "<email address hidden>" "Secr3t" "ec2-blah.amazonaws.com"

This will create an application token, which will then be listed at http://<host>/+applications if the user is logged in and the Ubuntu theme is enabled.

Testing this feature involves verifying that tokens are listed, and that token may be removed.

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.

Dave I know what I was got wrong. I copy pasted the http:// part of the url too.

Passes on ec2

Updated script to work with HTTPS servers in staging with bad certs.

This version additionally creates 3 tokens, named "Testing" "QA Superpowers" and "My Bug Finder".

Tested on Staging, added a new bug: https://bugs.launchpad.net/canonical-identity-provider/+bug/610212

This works well enough otherwise to be released for now.

Passes on Production