-- How setup Passport 3.4.4. & Gateway 6.11.4 as SFTP Client using Public key authentication in steps

# Configuration for Passport 3.4.4 on the Client side -

1. Have two local entities created in Passport under Security Management. One for holding Client''s private key (eg. tst4sshclnt ) & another for holding server''s public key (eg. tst4sshSvr).
2. Using Security Management, Public keys, Import the private key for the client associating it with the entity created for the same eg.. tst4sshclnt.
3. Using Security Management, Public keys, Import the public key for the server associating it with the entity created for the same eg.. tst4sshSvr.
4. Make sure the entities & the keys are all active, approved & updated to available status.
5. Have a remote partner created say, beautiful_partner.
6. Create a communication protocol say, testsshcomm of protocol type, Gateway Ssh-FTP, protocol mode Server, Category, Remote, label say    testsshcomm & organization, the partner name created in previous step, say beautiful_partner.
7. Under protocol tab, specify the remote directory path say / & then fill the ip address & port number for the remote SFTP server.
8. Choose public key as the client auth mode server, login user id as the login id configured for the client to login. You may want to give some dummy password if this screen requires you to do so but this will not be taken into account if you perform the next step.
9. Under server ssl, choose certificate type server as subject dn & certificate id server as the server''s public key entity associated in step 3 (eg.. tst4sshSvr)   providing the password for the same.
10. Depending upon the server used, choose the new line convention_server(windows/unix) & save.
11. Have a collaboration profile created & add the protocol to the same making it active & available with today''s date lying well between     the start date & the end date.

# Configuration of Gateway 6.11.4 on the Client side -

1. Make sure that SFTP is activated in the configuration menu > Connectivity > Internet Protocols (requires restart of Gateway)
2. Have a SSH Client profile defined say, SSH_CLNT_PROF under Security Management > Security Profile > SSH Profile.
  A. This profile should be of profile type client
  B. Enabled
  C. Make sure that one of the public key algorithms is specifically selected.
  D. Client Authentication methods set to public key
  E. Have the checkbox Trust hosted public key checked.
  F. In the Passport PS tab, local entity field, provide the passport entity name say tst4sshClnt & its password. This entity refers to    
     the entity in passport that carries the Private key of the client.
3. Create a generic remote site, say RS_SFTPOUT with all role & initialization modes checked.
  A. Have protocol selected as SFTP
  B. Do not fill anything on the n/w address
  C. In the SFTP tab, choose the SSH profile created in previous step, say SSH_CLNT_PROF & save the remote site.
4. Create a transfer model say with name, test_outbound with the following arguments
  application - default_B
  direction - O
  remote agent - The remote site name created in previous step, say RS_SFTPOUT
  tpm dea id - The alias for the communication protocol created in passport say testsshcomm
  type - trans
5. Create a transfer by choosing model as the model created in previous step say test_outbound, file component as the full path of the local file (eg. c:\testfile.txt ) & file name (eg. newfile.txt) as the remote file name.