Fork me on GitHub

Contents

Where is UPM's Config File

UPM's configuration file is named upm.properties. It's location it dependant on the version of UPM you're using.

In UPM 1.9 and earlier it's located in your home directory.

In UPM 1.10 and later it's location is dependant on your operating system.

Database Syncing

See Database Syncing for an overview of this feature.

Using Dropbox

To sync from one computer to another save your database file in your Dropbox folder. If you plan to sync to an Android device create the folder /Apps/UPM and save your database there. See Sync Using Dropbox on Android for more details.

When you make a change the database will be automatically saved and sync'd to your other machines. If you have a database open and a new version comes in over Dropbox UPM will alert you and ask if you'd like to load the new version.

Using a HTTP Server

See Sync Using HTTP for instructions on how to prepare your HTTP server.

There are generally two scenarios you can find yourself in terms of syncing. The first is where you have a password database on your PC that you'd like to upload to your server and make available for syncing to other devices. The second is where there's a password database already on your server and you'd like to sync it to your PC.

1. Uploading a database
  1. Open your database, Database -> Open Database
  2. Select Database -> Database Properties
  3. In the URL field enter the URL of your remote location. If you put the upload.php file at http://www.mydomain.com/upm/upload.php then enter http://www.mydomain.com/upm in the URL field. If this URL is password protected with basic authentication then select the account in your database that has the relevant username and password.
2. Downloading a database
  1. Select Database -> Open Database from URL
  2. Enter the URL of your database, e.g. http://www.mydomain.com/upm/upm.db. If the URL is protected with basic authentication enter the username and password. When all relevant fields are populated click OK
  3. The next dialog is titled Save Database As... and is asking where you'd like to save the downloaded database to. Select a dir, enter a file name and click Save.
  4. Finally, to open the downloaded database you'll be prompted to enter it's master password.

When the text "Revision x - Unsynchronised" appears in red in the status bar this means that your local and remote databases may by out of sync. To synchronise them press the Synchronise button or the select the menu item Database -> Sync with Remote Database. When the databases are in sync the status bar will read "Revision x - Synchronised".

Export to CSV

WARNING: Be extremely careful with your exported CSV file. It contains the entire contents of encrypted database in plain text.

Import from CSV

The UPM import CSV should be structured as follows, 

account name,user id,password,url,notes
Example: 
flickr,testuser,testpassword,http://www.flickr.com,some test notes

If an account in the CSV file exists in the database you'll be prompted for the action to take.

How to Add a Trusted HTTPS Certificate

NOTE:Since 1.12 you can choose to trust all self signed certificates rather than updating your keystore. While this is a much easier option it's not enabled by default as some may not like the security implications. To enable this setting use the "Accept Self-Signed Certificates" checkbox in the options dialog.

If you use a HTTPS URL for your remote database and the server is using a self signed certificate you may get this error when you try and sync,

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.

What you need to do is add the server's certificate to your trusted certificate keystore. Here's how,

Problem Running UPM on OS X

On downloading and running UPM on OS X you may get this error "UPM is damaged and can't be opened. You should move it to trash" or "UPM" can't be opened because it is from an unidentified developer. The problem is UPM hasn't been signed by Apple. There are two ways to work around this.

Option 1: Via System Preferences.

  1. Open System Preferences
  2. Open Security & Privacy
  3. If the lock in the bottom left of this window is closed click it to unlock the settings
  4. Under "Allow applications downloaded from" select "Anywhere"
  5. Try opening the version of UPM that was failing previously. If all goes well it should work now.
You can reset "Allow applications downloaded from" to what it was previously. OS X will remember that it's safe to open UPM.

Option 2: By updating the application's extended attributes directly.