YADE should support cs://(CredentialStore) syntax

Current Situation

• YADE configuration allow using of the KeePass databases
  • The definition of the configuration element CSEntryPath is required for every CredentialStoreFragment
    • that makes the use of CredentialStoreFragment element in a ProtocolFragment very inflexible

Desired Behaviour

• CSEntryPath should be optionally per a CredentialStoreFragment
• Referencing CredentialStore fields:
  • Referencing a field in the CredentialStore is effected by the following syntax:
    • cs://[entry_path]@entry_field
  • referencing in the ProtocolFragment and Proxy elements
    • Hostname, Account, Password, Passphrase, AuthenticationFile
      • Hostname - If the entry field value is defined with host:port, YADE sets the Hostname and Port automatically
  • fully specified entry path
  • relative path
  • referencing of the standard and custom fields

Examples

• Examples for fully specified entry path:
  • <Domain>, <Hostname>, <Account>, <Password>, <Passphrase> elements:
    • cs://sos/mft_server/srv001@title
    • cs://sos/mft_server/srv001@user
    • cs://sos/mft_server/srv001@password
    • cs://sos/mft_server/srv001@url
    • cs://sos/mft_server/srv001@notes
    • cs://sos/mft_server/srv001@my_custom_field
  • <AuthenticationFile> element:
    • cs://sos/mft_server/srv001@attachment - the first attachment
    • cs://sos/mft_server/srv001@my_custom_field - a specified attachment
• Examples without fully specified entry path:
  • <Domain> , <Hostname>, <Account>, <Password>, <Passphrase> elements:
    • cs://@title
    • cs://@user
    • cs://@password
    • cs://@url
    • cs://@notes
    • cs://@my_custom_field
  • <AuthenticationFile> element:
    • cs://@attachment - the first attachment
    • cs://@my_custom_field - a specified attachment