Skip to content

Commit

Permalink
feature/W-14557165
Browse files Browse the repository at this point in the history
  • Loading branch information
kevintroller committed May 29, 2024
1 parent cd1f215 commit 1dffbcf
Showing 1 changed file with 7 additions and 7 deletions.
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
= Configure Security Parameters of SSH Connection

The following example shows how to configure the Anypoint Connector for SFTP (SFTP Connector) to override security parameters using Anypoint Studio.
The following example shows how to configure the Anypoint Connector for SFTP (SFTP Connector) to override security parameters using Anypoint Studio.

== Create a Configuration Override File

Expand All @@ -19,9 +19,9 @@ MACs hmac-sha1,hmac-sha2-256,hmac-sha2-512
image::sftp-override-config-file-contents.png[Contents of the override config file]

[start=3]
. Configure the keys and values accordingly. If you do not provide any key, then default values are taken into consideration.
. Configure the keys and values accordingly. If you do not provide a key, then default values are used.

The following example shows where the config file is present in the`src/main/resources` folder:
The following example shows the location of the config file within the `src/main/resources` folder:

image::sftp-override-config-file-location.png[Location of the override config file]

Expand All @@ -33,9 +33,9 @@ Follow these steps to configure the override file:
. In the Choose Global Type window, type `sftp` in the search bar.
. Select *SFTP Config*.
. Click *OK*.
. Go to *Advanced* Tab.
. Under *Security Configuration* provide `SSH Config Override File`.
. Provide the path to the file. Example: `${app.home}/mule_sshd_config`.
. Go to the *Advanced* tab.
. Under *Security Configuration*, enter `ssh config override file`.
. Enter the path to the file, for example: `${app.home}/mule_sshd_config`.
. Complete the remaining connection fields.
. Click *Test Connection...*.
. Click *OK*.
Expand All @@ -56,7 +56,7 @@ In the *Configuration XML* editor window, the configuration looks like this:

Consider the following points when verifying the file creation:

* Search for the log `Read the config file` and verify that the filename and the configuration values fetched from the file are valid.
* Search for the log `Read the config file` and verify that the filename and the configuration values fetched from the file are valid.
* Find ignored configs with the log line `Config keys found but ignored`.
* Check that if the connector is unable to locate the file, then it logs `Couldn't locate config file`.

Expand Down

0 comments on commit 1dffbcf

Please sign in to comment.