...
Code Block |
---|
{{ [Keepass_DataBase_WithPassword] use_credential_Store = true CredentialStore_FileName = R:\backup\sos\java\development\com.sos.VirtualFileSystem\keepassX-test.kdb CredentialStore_KeyPath = sos/server/homer.sos CredentialStore_password = testing </source> <source> [ReceiveUsingKeePass] include = Keepass_DataBase_WithPassword source_CredentialStore_KeyPath = sos/server/homer.sos source_include = Keepass_DataBase_WithPassword source_Dir = /tmp/test/jade/out source_make_Dirs = true source_loadClassName = com.sos.VirtualFileSystem.FTP.SOSVfsFtp2 target_protocol = local target_dir = /tmp/test/jade/in operation = copy file_spec = \.txt$ transfer_mode = ascii source_transfer_mode = ascii loadClassName = com.sos.VirtualFileSystem.FTP.SOSVfsFtp2 </source> }} ==Parameter used by SOSCredentialStore== {| border="1" |+ List of parameter ! ! Name || title || mandatory || default |- | [[#CredentialStore_ProcessNotesParams|CredentialStore_ProcessNotesParams]] | Process additional parameters from "notes" filed | false | false |- | [[#CredentialStore_OverwriteExportedFile|CredentialStore_OverwriteExportedFile]] | CredentialStore_OverwriteExportedFile | false | true |- | [[#CredentialStore_Permissions4ExportedFile|CredentialStore_Permissions4ExportedFile]] | CredentialStore_Permissions4ExportedFile | false | 600 |- | [[#CredentialStore_DeleteExportedFileOnExit|CredentialStore_DeleteExportedFileOnExit]] | Delete Attachment On Exit of Application | false | true |- | [[#CredentialStore_ExportAttachment|CredentialStore_ExportAttachment]] | Export attached file to disc | false | false |- | [[#CredentialStore_ExportAttachment2FileName|CredentialStore_ExportAttachment2FileName]] | Name of the extracted attachment file | false | |- | [[#CredentialStore_KeyFileName|CredentialStore_KeyFileName]] | Name of the File containing the private Key | false | |- | [[#CredentialStore_password|CredentialStore_password]] | Password for CS | false | |- | [[#CredentialStore_AuthenticationMethod|CredentialStore_AuthenticationMethod]] | Authentication Method for the CS | true | privatekey |- | [[#CredentialStore_StoreType|CredentialStore_StoreType]] | The Type of the crendential store application | false | KeePass |- | [[#CredentialStore_KeyPath|CredentialStore_KeyPath]] | Path and Key for the credentials | true | |- | [[#CredentialStore_FileName|CredentialStore_FileName]] | Name of Credential Database | true | |- | [[#use_credential_Store|use_credential_Store]] | use credential store for authentication | false | false |} ====Parameter <span id="CredentialStore_ProcessNotesParams">CredentialStore_ProcessNotesParams</span>: Process additional parameters from "notes" filed==== ---- In "notes" filed of the CS Database extra parameters like DB connection string , Proxy server IP etc. can be defined. These paramters will be processed with the other parameters defined in settings file, JITL parameters, but "IMP" if an paramter with same name is defined in the "notes" section , parameter value in "notes" will have priority. {code:language=bash} -dburl=test -verbose=2 -password=12345-2 <source> |
Code Block |
---|
h2. example: of additional parameters in notes section
|
example: of additional parameters in notes section
-dburl=test -verbose=2 -password=12345-2
In the "notes" propertry of KeePass can be used to store extra parameters i.e. options such as DB
connetction connection string , proxy server settings etc.
Code Block |
---|
Data-Type : SOSOptionBoolean The default value for this parameter is {*}false{*}. Use together with parameter: * [use_credential_Store|#use_credential_Store] - use credential store for authentication Alias: CS_ProcessNotesParams h4. Parameter <span ih1. "CredentialStore_OverwriteExportedFile">CredentialStore_OverwriteExportedFile</span>: CredentialStore_OverwriteExportedFile ---- At runtime JADE can export the file defined in the attachment filed of the CS DB to the local file system. for example If attached file is an SSH key and JADE want to use the Key file for Data Exchange operation UsallyUsually if JADE want to use an SSH key , stored in the CS as attachement JADE has to export attached file into predefined directory i.e. $HOME/.ssh. To avoide any unwanted overwriting of any existing file into $HOME/.ssh folder, "IMP"" set this parameter as "false". Data-Type : SOSOptionBoolean The default value for this parameter is {*}true{*}. Use together with parameter: * [use_credential_Store|#use_credential_Store] - use credential store for authentication Alias: CS_OverwriteExportedFile h4. Parameter <span id"CredentialStore_Permissions4ExportedFile">CredentialStore_Permissions4ExportedFile</span>: CredentialStore_Permissions4ExportedFile ---- At runtime JADE can export the file defined in the attachment filed of the CS DB to the local file system. for example If attached file is an SSH key and JADE want to use the Key file for Data Exchange operation Usally if JADE want to use an SSH key , stored in the CS as attachement JADE has to export attached file into predefined directory i.e. $HOME/.ssh and key file should have specific permissions. It could be possible that "application user" calling the JADE have different set of application, to avoide any file permission issue during run time, "IMP" set the required file permission using these parameters {code:language=bash} -CredentialStore_Permissions4ExportedFile="600-MAHEND" <source> |
...