The Comm. Bridge passes a Common Format Buffers (CFB) that it receives from its clients to the server execution environment being served by the Comm. Bridge. The Comm. Bridge does not perform any security validation of its own. Additionally, the Comm. Bridge does not supply or add security data to a CFB. The originating client must specify the security data that is used. If security data is to be used for a given cooperative flow, the corresponding CFB must contain it such that it can be available for use by the Comm. Bridge.
The choice of which CFB security data the Comm. Bridge is to use depends on the type of CFB received, standard or enhanced. If the CFB is an enhanced CFB and the CFB header has the Use Client Manager Security flag set, then the security data comes from the CFB security offset area. Otherwise, the security data comes from the CFB header.
For more information about Comm. Bridge security, see the chapter "Communications Bridge Security." For more information about security within a Distributed Processing application, see the Distributed Processing – Overview Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|