Diagram
This element includes the parameters for access to a secure store with credentials for file transfer operations. If you want to store secure access data, i.e. account, password, SSH key, database connection strings, in an encrypted database, then configure access to a CredentialStore accordingly. A CredentialStore is a KeePass database that stores secure access data. Such credentials can be referenced from YADE configuration items instead of being exposed in plain text. Any number of CredentialStores can be configured. They are distinguished by their name attribute. References to a CredentialStore use the value of the name attribute to identify the respective CredentialStore. Use by configuration items Credentials can be referenced from a CredentialStore by the following configuration items: Any number of credential store fragments can be configured and are distinguished by YADE according to their name attribute. A fragment is referenced by a transfer Profile using the value of the CredentialStoreFragmentRef ref attribute. Support for KeePass versions 1 and 2. Note: Availability starting with YADE-464. Referencing CredentialStore fields. Note: Availability starting with YADE-481. Referencing a field in the CredentialStore is effected by the following syntax: cs://[entry_path]@entry_field where <Hostname> element: Examples This attribute identifies the current fragment. Any number of fragments can be used and are distinguished by YADE based on their name. A fragment is referenced via this attribute value by a transfer profile. This attribute identifies the current fragment. Any number of fragments can be used and are distinguished by YADE based on their name. A fragment is referenced via this attribute value by a transfer profile. This parameter specifies the path of the KeePass database file with the file extension .kdb or .kdbx that is used as a Credential Store database. A Credential Store can be accessed using a private key or using a password or a combination of both. A Credential Store can be accessed using a private key or using a password or a combination of both. A Credential Store can be accessed using a key file or using a password or a combination of both. Child elements include: Composite keys support: This parameter specifies the path to an entry inside the Credential Store database. At run-time YADE can export the file included with the attachment field of a Credential Store database to the local file system. Development status: not implemented At run-time YADE can export the file included with the attachment field of a Credential Store database to the local file system. To use the exported file during a file transfer operation YADE has to know the location of the attached file in the local file system. Use this parameter to specify the path of exported file in the local file system. Development status: not implemented At run-time YADE can export the file included with the attachment field of a Credential Store database to the local file system. With the file transfer operation being completed and irrespective of the operation's status YADE will by default delete this file. In special cases, e.g. for debuging, if you want YADE not to delete the file then use this parameter. Development status: not implemented At run-time YADE can export the file included with the attachment field of the Credential Store database to the local file system. For example if the attached file is an SSH key and YADE wants to use the key file for file transfer operations then YADE will export the attached file to a predefined directory, i.e. $HOME/.ssh. To avoid any unwanted overwriting of existing files in the $HOME/.ssh folder use this parameter. Development status: not implemented At run-time YADE can export the file included with the attachment field of the Credential Store database to the local file system. For example if the attached file is an SSH key and YADE wants to use the key file for file transfer operations then YADE will export the attached file to a predefined directory, i.e. $HOME/.ssh, and the key file will require specific permissions. A Credential Store can be implemented by different products. At the time of writing only "KeePassX" as a Credential Store database is supported and only KeePassX as valid parameter value is permitted.
CredentialStoreFragment
Notes
or the custom fields.
Element
Type
Required
Description
Attribute: name
NMTOKEN
Required
CSFile
string
Required
Notes
CSAuthentication
Required
PasswordAuthentication
Required
Notes
KeyFileAuthentication
Required
Notes
CSEntryPath
string
Optional
Notes
CSExportAttachment
Optional
Notes
CSExportedFile
string
Required
CSKeepExportedFileOnExit
boolean
Optional
CSOverwriteExportedFile
boolean
Optional
CSPermissionsForExportedFile
string
Optional
CSStoreType
string
Optional
Notes
References
References
References
References
References
References
References
Overview
Content Tools