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:
- Tap the Passify menu icon and tap "Settings"
- Scroll down to the "Provider" selector and choose which you wish to use
- 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.
Use a long encryption key Longer encryption keys are better for security. It is recommended to use at least 16-20 characters in your encryption keys.
The settings required from this point vary between Providers. Continue with the configuration steps below based on the provider you selected:
- Amazon S3, BackblazeB2
- Dropbox
- FTPS
- Google Drive
- iCloud
- MEGA
- Microsoft OneDrive
- NextCloud
- ownCloud
- pCloud
- SSH
- WebDAV
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:
- 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.
- Login to your Provider as normal
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.
- If authorization was successful, the web page will close and Passify will display a green check-mark. Tap the "Save" button to save your changes.
If the authorization failed, try again.
Amazon S3, BackblazeB2 (or compatible)
- Enter the Service URL for the Provider. For Amazon S3 this will be https://s3.amazonaws.com. If you are using a S3 Compatible Provider instead of Amazon, your Service URL will be different. Refer to your Providers documentation for information on the Service URL that you should use.
- Enter your existing Bucket Name for Passify to use
- Enter your S3 Access key. We recommend creating an Access Key specifically for Passify when possible.
- Enter your S3 Secret key. We recommend creating a Secret Key specifically for Passify when possible.
- Tap the "Save" button
FTPS
- Enter the Host name, Port, User Name and Password for the FTPS server. We recommend creating a unique User Name and Password specifically for Passify when possible.
- If you would like Passify to place its sync folder in a specific Path, enter it in the Path folder, beginning with a forward slash.
- 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 AppleID 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 into the site.
- Enter the User Name and Password for your account.
- 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 specificaly 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.
- 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 user name.
- Enter your NextCloud User Name 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.
- 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.
- 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.
- 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 user name.
- Enter your ownCloud User Name 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.
- 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.
- 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
- Enter the Host name, Port, User Name and Password for the SSH server. We recommend creating a special User Name and Password specifically for Passify when possible.
- If you would like Passify to place its sync folder in a specific Path, enter it in the Path folder, beginning with a forward slash.
- 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.
- Enter the WebDAV Service URL for your server.
- Enter the User Name and Password for your WebDAV server. We recommend creating a unique User Name and Password specifically for Passify when possible.
- 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.
- 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.