Passify

Configuring Sync

Configuring Passify to sync with a Provider

No matter which Provider you choose, you will perform these first few steps in order to configure Passify:

  1. Tap the Passify menu icon and tap "Settings"
  2. Scroll down to the "Provider" selector and choose which you wish to use
  3. Enter an encryption key for your sync data in the field at the top. You must use the same key on each device you wish to sync. Be sure to keep your encryption key in a safe place. If you use Passify to generate your encryption key, be sure to write it down or save it outside of Passify, because the Generator that creates it is stored in the data the key protects.

Use a long, random encryption key Anyone who gets a copy of your sync file can try unlimited guesses at your encryption key, so make it hard to guess: at least 16 random characters, or a passphrase of 6 random words. Don't reuse your Personal Secret or another password.

The settings required from this point vary between Providers. Continue with the configuration steps below based on the provider you selected:

Dropbox, Google Drive, Microsoft OneDrive, pCloud

These Providers all require you to log in and authorize Passify to access your account using an open standard known as Open Authorization (OAuth). Using OAuth, Passify does not need to know your login credentials, and you can revoke Passify's access at any time using the services' settings.

To configure one of these OAuth-based Providers:

  1. Note the red "X" indicating that Passify is not yet Authorized. Tap the "Authorize App" button to start the OAuth process. Passify will open a browser to the Provider's OAuth page.
  2. Login to your Provider as normal

  3. When prompted, authorize access to Passify.

    • Google Drive: Make sure you check the box labeled "See, create and delete its own configuration data in your Google Drive" or Passify won't be able to access your Drive.
  4. If authorization was successful, the web page will close and Passify will display a green checkmark. Tap the "Save" button to save your changes.

  5. If the authorization failed, try again.

Is your Provider login stored in Passify? AutoFill cannot be used on the Provider's login page, and you cannot leave the page to look up your credentials in Passify once it is open. Follow the steps below before you tap "Authorize App".

If your Provider's username and password (and one-time code, if you use two-factor authentication) are stored in Passify, you must have them in hand before starting the OAuth process:

  1. Copy your Provider's username and password from Passify and paste them into a temporary location, such as a notes app, a message to yourself, or a text field in another app.
  2. If your Provider requires a one-time code (TOTP), wait until Passify issues a new code, then copy it to the same temporary location. Codes expire quickly, so do not start the OAuth process until you are ready to move fast.
  3. Tap "Authorize App", then copy and paste your username, password and code into the Provider's login page. Complete the login before the code expires. Some Providers allow a little extra time, but many do not. If the code expires, close the page and start again with a fresh code.
  4. When the Provider shows that Passify is authorized, delete your temporary copies and clear your clipboard.

If you would rather not race the clock, you can temporarily turn off two-factor authentication for your Provider account while you authorize Passify. You will still need to copy your username and password beforehand. Be sure to turn two-factor authentication back on as soon as you are done, and save any new recovery codes it gives you.

You only need to do this when authorizing Passify on a device. Once authorized, Passify keeps its access without asking for your login again.

Amazon S3, Backblaze B2 (or compatible)

  1. Enter the Service URL for the Provider. For Amazon S3 this will be https://s3.amazonaws.com. If you are using an S3 Compatible Provider instead of Amazon, your Service URL will be different. Refer to your Provider's documentation for information on the Service URL that you should use.
  2. Enter your existing Bucket Name for Passify to use
  3. Enter your S3 Access key. We recommend creating an Access Key specifically for Passify when possible.
  4. Enter your S3 Secret key. We recommend creating a Secret Key specifically for Passify when possible.
  5. Tap the "Save" button

FTPS

  1. Enter the Host name, Port, Username and Password for the FTPS server. We recommend creating a unique Username and Password specifically for Passify when possible.
  2. If you would like Passify to place its sync folder in a specific Path, enter it in the Path field, beginning with a forward slash.
  3. Tap the "Save" button

Passify will attempt to validate the connection before saving your configuration. If a certificate issue occurs, Passify may prompt whether to accept the certificate before continuing.

iCloud

iCloud is limited to one Apple ID Due to technical limitations, syncing can only be performed between devices that are logged into the same iCloud account. If you need to share your Generators via sync with other individuals, please choose a different provider.

Before configuring Passify to use iCloud, make sure that iCloud is set up on your device, that you are logged in, and that Passify has access to iCloud services.

Once you have entered your Encryption Key and ensured that iCloud is configured on your device, tap the "Save" button

MEGA

MEGA requires you to use your same login credentials for Passify as you do to log in to the site.

  1. Enter the Username and Password for your account.
  2. Tap the "Save" button

MEGA does not support 2FA for automated logins If you have an existing, actively used MEGA account, we recommend that you open a separate free account specifically for your Passify data that does not have 2FA enabled.

Nextcloud

Nextcloud is configured using its built-in WebDAV interface. Passify requires a https:// address — a plain http:// server address will not be accepted.

  1. Enter the WebDAV Service URL for your Nextcloud server. This is typically in the form https://yourserver.com/remote.php/dav/files/username/, replacing "username" with your Nextcloud username.
  2. Enter your Nextcloud Username and Password. We recommend creating an app password specifically for Passify rather than using your main account password, especially if you have two-factor authentication enabled.
  3. If you would like Passify to place its sync folder in a specific Path under your Nextcloud files, enter it in the Path field, beginning with a forward slash.
  4. Tap the "Save" button

Passify will attempt to validate the connection before saving your configuration. If your server uses a self-signed or otherwise untrusted certificate, Passify will prompt you to accept or reject it before continuing.

ownCloud

ownCloud is configured the same way as Nextcloud, using its built-in WebDAV interface. Passify requires a https:// address — a plain http:// server address will not be accepted.

  1. Enter the WebDAV Service URL for your ownCloud server. This is typically in the form https://yourserver.com/remote.php/dav/files/username/, replacing "username" with your ownCloud username.
  2. Enter your ownCloud Username and Password. We recommend creating an app password specifically for Passify rather than using your main account password, especially if you have two-factor authentication enabled.
  3. If you would like Passify to place its sync folder in a specific Path under your ownCloud files, enter it in the Path field, beginning with a forward slash.
  4. Tap the "Save" button

Passify will attempt to validate the connection before saving your configuration. If your server uses a self-signed or otherwise untrusted certificate, Passify will prompt you to accept or reject it before continuing.

SSH

  1. Enter the Host name, Port, Username and Password for the SSH server. We recommend creating a special Username and Password specifically for Passify when possible.
  2. If you would like Passify to place its sync folder in a specific Path, enter it in the Path field, beginning with a forward slash.
  3. Tap the "Save" button

Passify will attempt to validate the connection before saving your configuration. If a certificate issue occurs, Passify may prompt whether to accept the certificate before continuing.

WebDAV

Passify's generic WebDAV provider works with most self-hosted or third-party WebDAV servers. If you are using Nextcloud or ownCloud, choose the Nextcloud or ownCloud provider instead for setup steps tailored to those servers. Passify requires a https:// address — a plain http:// server address will not be accepted.

  1. Enter the WebDAV Service URL for your server.
  2. Enter the Username and Password for your WebDAV server. We recommend creating a unique Username and Password specifically for Passify when possible.
  3. If you would like Passify to place its sync folder in a specific Path, enter it in the Path field, beginning with a forward slash.
  4. Tap the "Save" button

Passify will attempt to validate the connection before saving your configuration. If your server uses a self-signed or otherwise untrusted certificate, Passify will prompt you to accept or reject it before continuing.

Article Categories