A Java Proxy provides facilities to implement Distribute Processing Security, as described in the chapter of the Distributed Processing - Overview Guide.
By default, the Java 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 Java application that will set the ClientID and ClientPassword properties of the Java Proxy 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 Distributed Processing Server (DPS). In addition, if the client security user exit returns SECURITY_ENHANCED, the client security user exit(s) 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 Java Proxy flowing to a 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. See User Exits in this chapter, for a description of the user exits used to enable encryption and decryption processing for a Java Proxy.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|