Diagram
This element includes the parameters for an HTTPS file transfer connection including BasicAuthentication and URLConnection configuration items. Any number of 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 HTTPSFragmentRef ref attribute. This attribute identifies the current fragment. Any number of fragments can be used and are distinguished by YADE according their name. A fragment is referenced by a transfer profile using the value of this attribute. This attribute identifies the current fragment. Any number of fragments can be used and are distinguished by YADE according their name. A fragment is referenced by a transfer profile using the value of this attribute. A URL connection specifies parameters such as a Hostname, Port, Account by which a connection is established within the URL. The use of URLs depends on the server system, e.g. the following protocols and configuration items could be used: A URL connection specifies parameters such as a Hostname, Port, Account by which a connection is established within the URL. The use of URLs depends on the server system, e.g. the following protocols and configuration items could be used: Accept a valid certificate that could not be verified as being trustworthy. Usually a certificate verification process will always verify the DNS name of the certificate presented by the server, This setting can be used to disable the verification process of the hostname. When using this setting uses should be aware that this will reduce the credibility of certificate and therefore should be used exclusively for hosts that you trust. The BasicAuthentication element specifies the credentials for authentication with a server, e.g. using an FTP protocol or a Proxy Protocol. Child elements include: 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. Account for authentication at one of the systems involved in file transfer, e.g. an FTP or SFTP server. Usually the account corresponds to a user name. Should the respective server system be part of a Windows domain then the syntax domain\account can be used. 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 Password for authentication at a server that is involved in file transfer, e.g. with an FTP or SFTP protocol or Proxy protocol that makes use of BasicAuthentication. Passwords are not displayed in the YADE log files. A drawback is that passwords are visible in YADE configuration files. In order to avoid this you could switch to using File Transfer Protocols that allow SSHAuthentication, e.g. SFTP. 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 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. This attribute identifies the fragment that is used for inserting secure configuration items. 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. This attribute identifies the fragment that is used for a jump host. Proxies can make use of different protocols, a HTTPProxy - as the name suggests - will use the HTTP protocol HTTP proxies optionally support authentication. HTTP headers let the client and the server pass additional information with an HTTP request or response. This parameter specifies a HTTP header, which is used for a HTTP(S) file transfer. This parameter specifies the keystore type. Possible values: JKS,JCEKS,PKCS12,PKCS11,DKS This parameter specifies the keystore file. This parameter specifies the password of a keystore.
HTTPSFragment
Notes
Element
Type
Required
Description
Attribute: name
NMTOKEN
Required
URLConnection
[URLConnectionType]
Required
Notes
http|https :// [ account [ : password ] @ ] hostname [ : port ]
If the port is empty, the default ports will be used:
URLConnectionType / URL
anyURI
Required
http|https :// [ account [ : password ] @ ] hostname [ : port ]
If the port is empty, the default ports will be used:
AcceptUntrustedCertificate
boolean
Optional
Notes
DisableCertificateHostnameVerification
boolean
Optional
Notes
BasicAuthentication
[BasicAuthenticationType]
Optional
Notes
BasicAuthenticationType / Account
string
Required
or the custom fields.
BasicAuthenticationType / Password
string
Optional
or the custom fields.
CredentialStoreFragmentRef
Optional
JumpFragmentRef
Optional
Notes
ProxyForHTTP
Optional
HTTPProxy
[AuthenticatedProxyType]
Required
HTTPHeaders
Optional
Notes
YADE allows to specify HTTP headers individually per HTTP(S) transfer fragment or HTTP(S) transfer fragment reference.
HTTPHeader
string
Required
Notes
Name and value are separated by the first space, e.g.:
KeyStore
[KeyStoreComplexType]
Optional
KeyStoreComplexType / KeyStoreType
string
Optional
Notes
KeyStoreComplexType / KeyStoreFile
string
Required
Notes
KeyStoreComplexType / KeyStorePassword
string
Optional
Notes
References
References
References Notes
References
References
References
References Notes
References Notes
References Notes
References
References
References
References
References
References
Overview
Content Tools