Details
-
Feature
-
Status: Released (View Workflow)
-
Medium
-
Resolution: Fixed
-
1.13.15
-
None
Description
Current Situation
- With
YADE-577the SSHJ data provider was made available as an alternative to JSCH (JCraft). - Users who want to use SSHJ have to activate the data provider as JSCH is used by default
Desired Behavior
- SSHJ becomes the default provider for SSL based connections.
- JSCH works as a fallback and can be activated by the mechanisms explained with
YADE-577using the value "JSCH"
Test Instructions
- Note: do not use the Job/Order/YADE ssh_provider parameter.
- JITL-Jobs
- Configure and run the following JITL jobs that are processed with a JobScheduler Master:
- SSH Job
<script language="java" java_class="sos.scheduler.job.SOSSSHJob2JSAdapter">
- YADE Job
<script language="java" java_class="sos.scheduler.jade.JadeJob"/>
- Use a SFTP Transfer
- YADE DMZ Job
<script language="java" java_class="sos.scheduler.jade.SOSJade4DMZJSAdapter"/>
- SSH Job
- Repeat the Tests above - configure and run the jobs for processing with a JobScheduler Universal Agent.
- Configure and run the following JITL jobs that are processed with a JobScheduler Master:
- YADE Standalone Client
- Use a SFTP Transfer.
- Expected result:
- The SSH/SFTP operations should be executed with the SSHJ data provider.
- Find in the log output - SOSSFTPSSHJ
- The SSH/SFTP operations should be executed with the SSHJ data provider.
Attachments
Issue Links
- requires
-
YADE-577 SSH provider - support SSHJ
- Released