Using ubuntu-archive-tools and OpenID from remote shell's CLI

Launchpad uses OpenID for logon, and this is very problematic with ubuntu-archive-tools when running them in a remote shell's CLI (no X11, desktop environment, etc.)

1. OpenID logon uses `www-browser` for logon, which in most cases in a remote shell's CLI environment points to text-based `links`. Launchpad refuses to accept OpenID logon from `links` with "Bad bot, go away! Request aborted." message.

2. When running ubuntu-archive-tools in series, each command generates a new OpenID logon request.

3. OpenID tokens cannot be stored and reused between sessions. This is especially troublesome for doing automated scripting.

Can those be somehow worked around?