A .NET Proxy provides facilities to implement Distributed Processing Security.
Note: For more information about implementation of Distributed Processing Security, see the Distributed Processing - Overview Guide.
By default, the .NET Proxy does not exploit the use of the Proxy Runtime security features. To utilize the security features, the application developer must add code to the .NET application to set the ClientID and ClientPassword properties of the .NET Proxy Import view object. Depending on the return value of the client security user exit, the security data fields are sent to the target DPS. In addition, if the client security user exit returns SECURITY_ENHANCED, the client security user exits can add an optional security token to the data flow. User exits residing in the execution environment of the target DPS validate the collection of security data that is sent as part of the cooperative flow.
Note: For a description of the user exits available within each runtime environment supported by a .NET Proxy, see the User Exit Reference Guide.
For a .NET Proxy flowing to a DPS using TCP/IP or MQSeries 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. User exits enable the use of encryption and decryption.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|