|
|
|
|
|
|
How BEA Tuxedo Client Requests are Authorized
Authorization of client requests is based on each system's local mechanisms. The TEDG configuration and the names used for mapping requests are used in these authorization schemes. A BEA Tuxedo client request to a service name offered by the TEDG (DM_REMOTE_SERVICES) is subjected to standard BEA Tuxedo authorization by the TEDG in the same way that each server in a secure system is authorized. The TEDG then forwards the request to the BEA TOP END system, along with the local domain DOMAINID as the BEA TOP END client user ID. This request is not subjected to further security because the administrator has connected the BEA Tuxedo and BEA TOP END systems in a trusted relationship. When enqueuing requests to a BEA TOP END RTQ queue in a secure BEA TOP END system, the TEDG provides its local domain DOMAINID as the BEA TOP END client ID and its configured password (refer to the dmadmin topendpasswd command) as part of the request so that those client credentials can be used by RTQ when it dequeues the request and schedules shipment of it to a server.
See Also
|
|
|
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|