|
BEA eLink TCP for TUXEDO 3.0 Information Center | |
|
HOME | SEARCH | CONTACT | PDF FILES | WHAT'S NEW |
||
|
TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC | INDEX |
||
BEA eLink for Mainframe TCP for TUXEDO (hereafter referenced as eLink TCP for TUXEDO) uses data area security which is a specialized security protocol for the following cases:
In these cases, a client's USERID, group name, and LTERM can be specified in the data area of a request. For TUXEDO clients, user information specified in the data area is verified by the remote gateway in the usual manner. For remote clients, remote user information is placed in the data area fields by the local gateway to be used by TUXEDO services. In this case, the remote client does not have to populate these fields, but must allocate space for them in the data area.
Complete the following tasks to enable data area security.
Enabling Data Area Security
Note:
If using a VIEW data format, allocate the extra fields before the application data as defined in Listing B-1. If using the STRING data format, allocate 24 additional bytes at the beginning of the string to be used for the security fields.
The user data area fields in C use the following format.
Listing B-1 Syntax for C User Data Area Fields
struct da_security {
char uname[8]; /*user name*/
char group[8]; /*user group*/
char lterm[8]; /*terminal id*/
/*user data is appended here*/
}