YADE Parameter Reference - WebDAVFragment

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.

• Schema: URLConnection, URLConnection
• Mapping:
  • auth_method

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:
http|https :// [ account [ : password ] @ ] hostname [ : port ]
If the port is empty, the default ports will be used:

• HTTP: 80
• HTTPS: 443

• Schema: AcceptUntrustedCertificate, AcceptUntrustedCertificate
• Mapping:
  • accept_untrusted_certificate

Accept a valid certificate that could not be verified as being trustworthy.

• Trustworthy certificates
  • are issued by certificate authorities.
  • can be verified by their signature.
• Untrustworthy certificates
  • include e.g. self-signed certificates.
  • cannot be verified, instead, you have to trust them.
• Invalid certificates
  • cannot be processed.
  • could e.g. be expired or issued for a different host.

• Schema: DisableCertificateHostnameVerification, DisableCertificateHostnameVerification
• Mapping:
  • verify_certificate_hostname

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.

• Schema: BasicAuthentication, BasicAuthentication

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.

• Schema: CredentialStoreFragmentRef, CredentialStoreFragmentRef

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.

• Schema: JumpFragmentRef, JumpFragmentRef

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.

ProxyForWebDAV - will use the HTTP proxy

• Schema: HTTPProxy, HTTPProxy
• Mapping:
  • proxy_protocol
• Release:
  • YADE-351 Availability starting with 1.11.

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

HTTP proxies optionally support authentication.

• Schema: KeyStore, KeyStore

This parameter specifies the storage facility for cryptographic keys and certificates.

Notes

• WebDAV - Availability starting with YADE-582.

• Schema: KeyStoreType
• Mapping:
  • keystore_type

This parameter specifies the keystore type. Possible values: JKS,JCEKS,PKCS12,PKCS11,DKS

• Schema: KeyStoreFile
• Mapping:
  • keystore_file

This parameter specifies the keystore file.

• Schema: KeyStorePassword
• Mapping:
  • keystore_password

This parameter specifies the password of a keystore.