Skip to end of metadata
Go to start of metadata

Diagram

Elements

FTPFragment
References Notes

This element includes the parameters for an FTP file transfer connection including BasicAuthentication and BasicConnection configuration items.

Any number of fragments can be configured and are distinguished by YADE according to their name attribute. Therefore a unique identifier should be specified for the name attribute.

A fragment is referenced by a transfer Profile using the value of the FTPFragmentRef and its ref attribute.

name

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.

Element Type Required Description
Attribute: name NMTOKEN
Required

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.

BasicConnection [BasicConnectionType]
  • Occurrence: 1
Required
References Notes

A connection specifies parameters for a Hostname and a Port to which a connection is established.

BasicAuthentication [BasicAuthenticationType]
  • Occurrence: 1
Required
References Notes

The BasicAuthentication element specifies the credentials for authentication with a server, e.g. using an FTP protocol or a Proxy Protocol. Child elements include:

  • Account for authentication. For Windows Systems an account could include the domain.
  • Password for authentication. Passwords are not displayed in the YADE log files.

BasicAuthentication is available for a number of File Transfer Protocols and Proxy Protocols. The drawback with BasicAuthentication is that passwords are stored directly in configuration files. In order to avoid this you could switch to using File Transfer Protocols that allow SSHAuthentication, e.g. SFTP.

CredentialStoreFragmentRef
  • Occurrence: 0..1
Optional
References Notes

This element references the fragment that is used to insert configuration items from a secure store into a file transfer configuration.

Any number of reusable CredentialStoreFragment elements can be configured and are distinguished by YADE based on their name attribute.

The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the CredentialStoreFragment element.

Support for a jump host.

Note: Availability starting with YADE-488.

ref

This attribute identifies the fragment that is used for inserting secure configuration items.

JumpFragmentRef
  • Occurrence: 0..1
Optional
References Notes

Any number of reusable JumpFragment elements can be configured and are distinguished by YADE based on their name attribute.

This element identifies the JumpFragment that is applied for use of a jump host in a file transfer.

The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the JumpFragment element.

ref

This attribute identifies the fragment that is used for a jump host.

PassiveMode boolean
  • Whitespace: collapse
  • Occurrence: 0..1
Optional
References Notes

Passive mode is often required for FTP transfers with firewalls.

TransferMode string
  • Whitespace: preserve
  • Enumeration:
    • binary
    • ascii
  • Occurrence: 0..1
Optional
References Notes

Transfer mode is used only for FTP and can be either ascii or binary.

ProxyForFTP
  • Occurrence: 0..1
Optional

ProxyForFTP - will use the HTTP, SOCKS4 or SOCKS5 proxy

HTTPProxy [AuthenticatedProxyType]
  • Occurrence: 1
Required
References Notes

Proxies can make use of different protocols, a HTTPProxy - as the name suggests - will use the HTTP protocol

HTTP proxies optionally support authentication.

SOCKS4Proxy [UnauthenticatedProxyType]
  • Occurrence: 1
Required
References Notes

Proxies can make use of different protocols, a SOCKS4Proxy - as the name suggests - will use the SOCKS4 protocol

SOCKS4 proxies do not support authentication.

SOCKS5Proxy [AuthenticatedProxyType]
  • Occurrence: 1
Required
References Notes

Proxies can make use of different protocols, a SOCKS5Proxy - as the name suggests - will use the SOCKS5 protocol

SOCKS5 proxies optionally support authentication.

Note

The CheckServerFeatures and ControlEncoding parameters have been deleted from version 1.12. See JADE-340 - Getting issue details... STATUS for more information.



  • No labels
Write a comment…