Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 16

changes.mady.by.user Alan Amos

Saved on

compared with

New Version Current

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

  • A jump  jump host is a server over which traffic to and from a network is channeled, see Jump Host Architecture.
  • Jump hosts can be used to provide a secure method of file transfer across network boundaries by not allowing direct transfer over the boundary.
  • DMZs  (demilitarized zones) are a common form of jump hosts.
  • JADE YADE can be used to carry out file transfer via a jump host, once a JADE client YADE Client has been installed on the jump host.
  • A wider range of Different protocols can be used for transfer between the target source host and the jump host than for the transfer to/from between the jump host and the target host. To this end, different parameter sets are defined in the JADE YADE configuration for each part of the transfer.JADE has been written so that from the standpoint of the application originating the file transfer, transfer between the JADE client and the jump host and transfer between the jump host and the remote server are specified as a single operation. The part of the configuration specifying transfer between the client and the jump host is then called as a reference from the part of the configuration specifying the transfer from the jump host to the remote server.
    This means that the jump host effectively remains transparent to the JADE client. 

The focus of this article is the configuration of individual parameters - a more general description of the considerations involved in setting up a jump host file transfer can be found in the following article:

Schematic Diagram

The following diagram shows schematically how files are sent via the Internet from one network with a DMZ to another network with a DMZ.

 

Configuration 

The XML element hierarchy for the configuration of a jump host is shown below for a Copy operation with the jump host on the target side of the operation:

  • Fragments
    • ProtocolFragments
      • *Fragment (any protocol except SMB can be used for transfer from jump host to target)
        • *Connection
        • *Authentication
        • JumpFragmentRef  (References references the JumpFragment)
        • etc.
      • JumpFragment
        • BasicConnection
        • SSHAuthentication
        • JumpDirectory (optional)
        • ProxyForSFTP (optional)
        • StrictHostKeyChecking (optional)
  • Profiles
    • Profile
      • Operation
        • Copy
          • CopySource
            • CopySourceFragmentRef
          • CopyTarget
            • CopyTargetFragmentRef
            • Directory

As already mentioned , the jump host is transparent to the JADE client. A fragment element is specified in the usual manner and is called from a CopySourceFragmentRef or CopyTargetFragmentRef element in the Profiles branch of the configuration.

The jump host is specified as part of the configuration of the file transfer fragment using the JumpFragmentRef element, which can be specified as an optional child of all connection fragment elements, with the exception of SMBFragments.

...

Neither configuration data nor log files are stored by JADE YADE on the jump host.

Element Restrictions

Element Use Restrictions

  • Only a single JumpFragment can be specified as part of a connection fragment element.

    Jump hosts cannot be specified as part of AlternativeFragment elements.

Parameter Restrictions

  • BasicConnection and SSHAuthentication elements must be specified for every JumpFragment. URL- and HTTPConnections and BasicAuthentication are not allowed.
  • Password or Publickey authentication can be specified
  • Only SFTP proxies can be used with JumpFragment elements, meaning that only proxies that use the SOCKS4 and SOCKS5 protocols can be specified.

Parameter Reference

Examples

Tutorial