Set credentials for a volume

It is possible to associate credentials to volumes, to be used when accessing volumes that are located in shares in a separate domain. (This could happen for GNPortal servers in the DMZ storing data in volumes inside the firewall).

The volume definitions now include optional login credentials: user name, domain and password.

If a volume has credentials and corresponds to a share (i.e. it is defined as \\server\sharename\... or as file://server/sharename/....) the system automatically log-in to the server hosting the share executing the equivalent of a 'net use' command.

Here is a sample volume definition file including credentials:

<?xml version="1.0"?>

<Volumes 

  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 

  xmlns:xsd="http://www.w3.org/2001/XMLSchema" 

  xmlns="http://www.teradp.com/schemas/GN4/1/Volumes.xsd">

  <VolumeDesc 

    Name="images" 

    Url="file://server1/VolumeImages/" 

    UserName="user1"

    Domain="domain1"

    Password="pwd1"

    IsRemovable="false" 

    IsReadOnly="false" />

  <VolumeDesc 

    Name="videos" 

    Url="\\server2\VolumeVideos\" 

    UserName="user2"

    Domain="domain2"

    Password="pwd2"

    IsRemovable="false" 

    IsReadOnly="false" />

    -->

</Volumes>

to be imported using:

srv4 volumes -in volumes.xml

Volumes created automatically by the system based on the default volumes URL root ('Db.RootVolumeUrl' in the application settings) are always without any credentials. The only way to define volumes with credentials is importing the XML volume definition.

If there are multiple volumes all defined on the same server the system will log-in only once - using the credentials of the first volume it loads for that server.

The structure of the database has changed: there are three new columns in gn_VolumeTable. It is necessary to update it using:

srv4 dbupdate -s .......  -d ""

Passwords are stored in the database in the gn_Password column of gn_VolumeTable as encrypted binary data. The encryption uses the same mechanism and pass-phrase used by the encryption of 'password' attributes defined in the schema.