FTP Reverse Proxy configuration
The FTP configuration scenarios describe how to configure FTP protocol connections to and from the Secure Proxy engine.
Known Consideration
Sterling B2B Integrator Server Adapters support SSL session caching when Secure Proxy FTP Server Adapters connect to the outbound FTP node (representing the B2Bi FTP Server Adapter) in its netmap. This allows for abbreviated SSL negotiation (abbreviated handshaking) and allows the engine to reuse a session id of a previously connected session. This improves the performance of the system as it does not have to go through the full handshaking process to authenticate the connection between SSP and Sterling B2B Integrator.
Since the two endpoints use an abbreviated handshaking, the SSL connection parameters modified via the Configuration Manager GUI and pushed to Engine may become effective only after some delay.
Organization of the FTP Configuration Scenarios
The first scenario instructs you how to configure a basic configuration. Each successive scenario adds a security feature to the basic configuration. After adding a security feature, test the connection to ensure that you have correctly configured it. You determine your security needs and configure the security features applicable for your environment.
- Create a basic FTP configuration
- Add SSL/TLS support
- Perform user authentication using the local user store
- Provide outbound credentials using the netmap
- Authenticate an inbound certificate or user using Sterling External Authentication Server
- Manage connection requirements to the outbound server using Sterling External Authentication Server
- Define alternate nodes for failover support
- Define a passive data outbound port range for an FTP Reverse Proxy adapter
- Define a passive NAT address for an FTP Reverse Proxy adapter
- Define an active data outbound port range for an FTP Reverse Proxy adapter