Connect:Direct Proxy configuration
The Connect:Direct® configuration scenarios describe how to configure Connect:Direct protocol connections to and from the Secure Proxy engine with the Configuration Manager.
Attention: Configuration information must be available
at the engine before communication sessions with Connect:Direct can be
established.
Organization of the Connect:Direct Configuration Scenarios
The first scenario instructs you how to do a basic setup. Each successive scenario adds a security feature to the basic configuration. After you go through each scenario, test the connection to ensure that it is correctly configured. You determine your security needs and configure the security features applicable to your environment.
The
scenarios include:
- Create a basic Connect:Direct configuration
- Add SSL/TLS support
- Configure PNODE-based routing
- Add local user authentication
- Copy data or run a program that is based on the success or failure of a Connect:Direct Process step
- Block Connect:Direct tasks from a PNODE
The remaining configuration scenarios require Sterling External Authentication Server Server,
an optional security feature of Secure Proxy that must
be configured independently of Secure Proxy. After Sterling External Authentication Server is
configured, you can update your basic security definitions to enable Secure Proxy to connect
to Sterling External Authentication Server to
enforce the following advanced security features:
- Authenticate an inbound certificate or user with Sterling External Authentication Server
- Configure user mapping
- Configure certificate-based routing
- Perform user mapping to the SNODE with Sterling External Authentication Server
Additional procedures are provided to instruct you how
to configure the following features:
- Define alternate nodes for failover support
- Enable action that is based on protocol errors