IBM Support

Connecting to IBM Sterling B2B Integrator (SBI) SFTP SERVER using another SBI client through public key authentication with SSH remote profiles

Technical Blog Post


Abstract

Connecting to IBM Sterling B2B Integrator (SBI) SFTP SERVER using another SBI client through public key authentication with SSH remote profiles

Body

This blog demonstrates how to configure IBM Sterling B2B Integrator (SBI) SFTP Server Adapter for key based authentication and also SBI as Client but using SSH remote profiles.

In this demonstration I have used two SBI instance (one SBI instance as SFTP Client and another one as SFTP Server)

Client: http://X.XXX.XXX.124:11000/dashboard/portal/

Server: http://X.XXX.XXX.240:11000/dashboard/portal/

1. Log on to the SBI dashboard application and navigate to Deployment > SSH Host Identity Key and create New SSH Host Identity Key and save the key.

2. Then create new SFTP Server Adapter from Dashboard > Deployment > Services page. When creating the SFTP Server Adapter choose the Host Identity Key created in step 1. Andalso choose the Required Authentication as "Public Key". Then save the configuration and note down the SFTP Server Adapter port number.

image

3. Then on the SFTP Client side create a user identity key from Trading Partner > SSH > User Identity Key section.

image

4. Export the user identity key created in step 3 and check-in the key into server by navigating to Trading Partner > SSH > Authorized User key section.

image

5. Associate the server user (in this case admin) with the authorized key that checked-in step 4.

image

6. Create a SSH Remote Profile on client by navigating to Trading Partner > SSH > Remote Profiles menu. And choose the public key authentication method.

image

7. Create a simple business process (BP) with the profile id generated for the remote profile created.

<process name = "SFTP_Client_Test">

<sequence>

<operation name="SFTP Client Begin Session Service">

<participant name="SFTPClientBeginSession"/>

<output message="SFTPClientBeginSessionServiceTypeInputMessage">

<assign to="." from="*"></assign>

<assign to="SFTPClientAdapter">SFTPClientAdapter</assign>

<assign to="ProfileId">43594714e523bc6c7node1</assign>

</output>

<input message="inmsg">

<assign to="." from="*"></assign>

</input>

</operation>

<operation name="SFTP Client End Session Service">

<participant name="SFTPClientEndSession"/>

<output message="SFTPClientEndSessionServiceTypeInputMessage">

<assign to="." from="*"></assign>

</output>

<input message="inmsg">

<assign to="." from="*"></assign>

</input>

</operation>

</sequence>

</process>

8. Execute the BP and it should be successful.

image

We are now done with public key authentication. The SFTP client now connected to the SFTP server without password but key based using remote profile configuration.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

UID

ibm11121901