Page History

...

Scope

This article describes a relatively simple example configuration to illustrate the use of the Credential Store. This example can be  with the YADE Client using a relatively simple example configuration and the JobScheduler JADE JITL job using to allow users to get a working Credential Store up and running as easily as possible.

...

• Compliance:
  • All sensitive configuration information is encrypted.
  • Access to the Credential Store can be securely protected by password, key file or password and key file.
    "Password-free" authentication is possible.
  • Connection Authentication files such as public key files are used without being written to the file system.
• Management
  • Configuration information can be centrally managed outside of a file transfer environment.
• Deployment
  • The same file transfer configuration file can be used for development and production environments - only the Credential Store needs to be changed during deployment.
• Scope
  • The Credential Store can be used for the following configuration information:
    • file transfer source, target, proxy and  jump host / DMZ,
    • pre- and post-processing operations.
  • The Credential Store can be used for file transfers carried out with both the YADE Client and the JobScheduler JADEJob and JADE4DMZJob JITL jobs.
• Database Format and Applications
  • The Credential Store uses the standard .kdb or .kdbx open database formats. A number of commercial and open source tools are available for configuring these database formats on a range of operating systems. These tools include KeePass 1.x, KeePass 2.x and KeePassX. 

Anchor
example example

Example Description

...

Note that custom parameters can only be used to set parameters in ProtocolFragments - they cannot be used to set ProfileFragments parameters such as Recursive.

See Also

...

• YADE User Manual - Credential Store

References

Support of this feature is subject to the following features:

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-462

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-464

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-481

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-482

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-485

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-487

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-491

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-498