SparkLabs Forum.

Community Help.


Export/Import Connections

Hello Viscosity team,

There has to be an easier way to export, and by extension, importing connections. Currently, I have to export each connection one by one. I can't even select multiple connections to export (gets grayed out) nor can I select the folder it's in and export the whole thing. When I import, I am forced to import it one by one, quite tedious when I have over 15 VPN server connections to import. Also regarding importing connections, the user/login credentials for each connection is lost so I have to manually type/copy/paste the credentials for EACH connection, even when they are the same credentials. I really don't understand why when you export the connection, it doesn't save the settings/credentials along with it, makes no sense to me.

Thank you for your time.
Hi jsmita,

Thanks for your feedback - much appreciated.

A few inline comments to help you use Viscosity as it currently stands:

Currently, I have to export each connection one by one. I can't even select multiple connections to export (gets grayed out) nor can I select the folder it's in and export the whole thing.

If distributing connections to other users our recommend method is to make use of Viscosity's bundling feature. More information on this can be found in the following articles:
http://www.sparklabs.com/support/bundling_viscosity/
http://www.sparklabs.com/support/viswin ... viscosity/

When I import, I am forced to import it one by one, quite tedious when I have over 15 VPN server connections to import.

It's possible to import multiple connections in one go by selecting the folder they are located in. That is, click the "+" button in Viscosity's Connections section, select Import Connection->From File, and select the folder where your connections are stored. Viscosity will automatically search the folder (and any sub folders) for connections and import them. Alternatively you can make use of Viscosity's bundling feature to automatically bundle the client with a large number of connections.

I really don't understand why when you export the connection, it doesn't save the settings/credentials along with it, makes no sense to me.

This is a security design decision: saving a username/password in this fashion would be too insecure. If distributing user-specific connections the recommended method is to make use of OpenVPN's PKI support and generate unique certificate/key pairs for each user (this approach is also more secure).

Cheers,
James
2 posts Page 1 of 1

Copyright © 2016 SparkLabs Pty Ltd. All Rights Reserved. Privacy Policy