A COM Proxy provides facilities to implement Distributed Processing Security as described in the Distributed Processing - Overview Guide.
By default, the COM Proxy does not exploit the use of the Proxy Runtime security features. To utilize the security features, the application developer must add code to their COM application to set the ClientID and ClientPassword properties of the COM Proxy's Import view object. Depending on the return value of the client security user exit, the security data fields will or will not be sent to the target DPS. Additionally, 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 a COM Proxy flowing to a DPS using TCP/IP, MQSeries or ECI the supporting runtime lets a portion of the Common Format Buffer (CFB) 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.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|