uptrack-api-authorize uses the authorize API call to change the authorization for a single machine, for example:

$ uptrack-api-authorize -u api_username -k api_key uuid deny
Successfully denied access for uuid.
$ uptrack-api-authorize -u api_username -k api_key uuid allow
Successfully allowed access for uuid .

uptrack-api-describe uses the describe API call to get detailed information on a single machine specified by its UUID, for example:

$ uptrack-api-describe -u api_username -k api_key uuid
    prod1.mydom.com (192.168.1.100)
    Effective kernel: 2.6.18-194.11.1.el5
    This machine is no longer active
    Last seen on 2010-09-12T10:19:35Z
    OS status: Up to date

Alternatively, specify the --this-machine option if you are running the script on the machine that you want to check:

    $ uptrack-api-describe -u api_username -k api_key --this-machine
    qa.mydom.com (192.168.1.200)
    Effective kernel: 2.6.18-194.8.1.el5
    This machine is active
    Last seen on 2010-09-15T12:43:07Z
    OS status: Out of date:
      * Install v8gacfip CVE-2010-2521: Remote buffer overflow in NFSv4 server.
      * Install 3c4sopia CVE-2010-2226: Read access to write-only files in XFS filesystem.
      * Install oiqwvltu CVE-2010-2240: Privilege escalation vulnerability in memory management.

uptrack-api-list uses the machines API call to return a list of all of your machines and their statuses, for example:

$ uptrack-api-list -u api_username -k api_key
    - dev1.mydom.com (192.168.1.102): outofdate
    - qa1.mydom.com (192.168.1.103): outofdate (inactive)
    - prod1.mydom.com (192.168.1.100): uptodate
    - prod2.mydom.com (192.168.1.101): uptodate

If you set the username and api_key variables in the configuration file /etc/uptrack-api.conf, you do not need to supply these variables as command line arguments to the scripts. Place the variables under an [uptrack] section heading, for example:

[uptrack]
username = jo.admin@mydom.com
api_key  = 3af3c2c1ec407feb0fdc9fc1d8c4460c 

You can also set the user name and api key in the UPTRACK_API_USERNAME and UPTRACK_API_KEY environment variables, for example:

$ export UPTRACK_API_USERNAME=jo.admin@mydom.com
$ export UPTRACK_API_KEY=3af3c2c1ec407feb0fdc9fc1d8c4460c
$ uptrack-api-describe --this-machine

If you access the Internet via a proxy, specify the connection information in the [uptrack] section of /etc/uptrack-api.conf:

https_proxy = [protocol://][username:password@]proxy[:port] 

For example:

https_proxy = http://proxy.example.com:3128/

The proxy must support HTTPS connections.