Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SFTP / SCP connectors missing authentication options to use a private key #1157

Closed
brokenjacobs opened this issue Nov 15, 2022 · 2 comments · Fixed by #1172
Closed

SFTP / SCP connectors missing authentication options to use a private key #1157

brokenjacobs opened this issue Nov 15, 2022 · 2 comments · Fixed by #1172
Assignees
Milestone

Comments

@brokenjacobs
Copy link

brokenjacobs commented Nov 15, 2022

These settings collectively are:

camel.sink.endpoint.privateKey | Set the private key as byte so that the SFTP endpoint can do private key verification.
camel.sink.endpoint.privateKeyFile | Set the private key file so that the SFTP endpoint can do private key verification.
camel.sink.endpoint.privateKeyPassphrase | Set the private key file passphrase so that the SFTP endpoint can do private key verification. |
camel.sink.endpoint.privateKeyUri | Set the private key file (loaded from classpath by default) so that the SFTP endpoint can do private key verification.

Settings are also missing for hostkey checking, and providing a known hosts entry for the remote for validation:
camel.sink.endpoint.strictHostKeyChecking
camel.sink.endpoint.useUserKnownHostsFile

Setting a private key and known hosts file is usually done for ssh applications and is not possible with the current Kamelet.

@oscerd
Copy link
Contributor

oscerd commented Nov 16, 2022

for SFTP this is a duplicate of: #778

@oscerd oscerd added this to the 0.10.0 milestone Nov 18, 2022
@oscerd
Copy link
Contributor

oscerd commented Nov 22, 2022

I would avoid the privateKey parameter and just use the privateKeyFile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants