|
|
|
|
|
|
How the TEDG Supports Security
Both the BEA TOP END and BEA Tuxedo systems offer integrated security services. The TEDG works with both sets of services. Authentication of client applications is the responsibility of the local system and is performed in the same way for all configurations, regardless of whether the TEDG is included.
The only consideration to keep in mind when programming security for a configuration that includes a TEDG is that different functions are used in the BEA Tuxedo and BEA TOP END systems to specify client identifiers and passwords to the local programming interfaces. In BEA Tuxedo code, this task is done through the tpinit(3c) function; in BEA TOP END code, through the tp_client_signon(3T), tp_rtq_signon(3T), and tp_rtq_put(3T) calls. In a BEA Tuxedo application, one ID is used for a client program; in a BEA TOP END application, a separate client ID is associated with each dialog. For an administrator's view of security administration on TEDG-based configurations, refer to Configuring Security Between BEA TOP END and BEA Tuxedo Systems.
See Also
|
|
|
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|