Previous Topic: Using a C ProxyNext Topic: Overview of an Example Makefile for Windows


Security Processing

A C Proxy provides facilities to implement Distributed Processing Security as described in the Distributed Processing - Overview Guide.

To utilize the security features, the application developer must add code to their user-written C/C++ application that sets the ClientUserid and ClientPassword parameter of the parameter block that is to be sent to the server. Depending on the return value of the client security user exit (WRSECTOKEN), the security data fields will or will not be sent to the target DPS.

If the client security user exit returns SECURITY_ENHANCED, the client security user exits can cause an optional security token to be added to the data flow. The collection of security data that is sent as part of the cooperative flow is validated by user exits residing in the execution environment of the target DPS.

For user-written C/C++ applications flowing to DPS using TCP/IP, MQSeries, or ECI the supporting runtime lets a portion of the Common Format Buffer to be encrypted on the way to the target DPS, and decrypted on the way back from the target DPS. The use of encryption and decryption are enabled by way of user exits (WRSECENCRYPT and WRSECDECRYPT respectively).

More information:

Configuring the C Proxy at Runtime