Date: Fri, 29 Mar 2024 06:40:48 +0000 (UTC) Message-ID: <845134768.12483.1711694448608@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12482_2141378459.1711694448608" ------=_Part_12482_2141378459.1711694448608 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The YADE Credential Store offers a central and secure location to store = credentials rather then specifying, for example, information such as the us= er name and password in configuration parameters.
Use of the Credential Store therefore ensures compliance.
Credential Stores are KeePassX databases that have = been configured to be used by YADE. They are not related to the Java Keysto= re that can be used by specifying FTPSClientSecurity parameters.
Credential Store elements are referenced from a configuration profile in= a similar manner to the way file transfer protocol and notificat= ion fragments are referenced:
Any number of Credential Store elements can be configured within a file = transfer configuration.
The XML Hierarchy for Credential Store elements is shown schematically i= n the section below and more detailed information about the configuration o= f the individual credential store elements can be found in the following Pa= rameter Reference articles:
The following diagram shows the XML element hierarchy required to specif= y two credential stores, CS-1 and CS-2.
The CS-1 ref attribute of the CredentialStoreFragmentR= ef element in the transfer profile is used to call the CredentialS= toreFragment with the name CS-1. This element then contains t= he necessary information necessary to access the authentication information= saved in the credential store.
A more detailed description of the use of the Credential Store can be fo= und in the Using Credential S= tore to securely store authentication, connection and other parameters = article.