Customer Portal

private key for connecting to sftp (schedules)

Comments 3

  • Avatar
    Hana Habrzettlova
    0
    Comment actions Permalink

    Hi Igne, 

    Would you mind describing your use case a bit? Could you give us an example of what you are looking to do? It would help us get a better understanding of what your goal is and we can then provide you with a specific answer to your scenario. 

    Thank you!

    Hana

  • Avatar
    Igne Tarasova
    0
    Comment actions Permalink

    Hi Hana,

    thanks for the reply. I am looking to utilising the same key for both listeners and schedules.

    In our case, the user both reads and writes files to sftp. We use the listener (file listener to be precise) to grab the latest file, here the ssh-config with identity file location works good. 
    However, we also have some scheduled jobs that need to output data to the sftp. Certainly that could be achieved by, as you advise, placing the key file in project folder.
    However, it would be much easier if the keyfile that already is used by the listener, could also be accessible for the schedules (f.x. pointing to the ssh-config/location through sandbox parameters or similar) - I assume it is also possible via workaround by coupling scheduler with a listener, but that seems to be a bit of a redundant step.

    The key file placement used by listeners in our case is more secure and stable as we tend to overwrite/update sandboxes quite a lot.

    Best regards,
    Igne

  • Avatar
    Lukas Cholasta
    0
    Comment actions Permalink

    Hi Igne,

    In this case, keys for listeners and for schedulers should work the same. In other words, while you have the keys correctly set for listeners, the same set of keys should be working for schedulers as well. If you have any issues, please send us screenshots of the issue as well as the support package which is downloadable from the CloverDX Server console -> Configuration -> System Info.

    Thank you and best regards,

    Lukas

Please sign in to leave a comment.