How Security Is Handled by the TEDG


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Using the BEA Tuxedo TOP END Domain Gateway \| Local Topics \| Previous Topic \| Next Topic \| Contents

How Security Is Handled by the TEDG

The TEDG handles security in a manner similar to how the BEA Tuxedo TDomain handles security.

The local BEA Tuxedo domain or BEA TOP END system controls access for local clients. Clients log in once to their respective systems, and are authenticated and authorized according to the local policy.
The TEDG allows an administrator to control access to BEA TOP END services by BEA Tuxedo clients. Similarly, the administrator can control access to BEA Tuxedo services from the BEA TOP END system.
Requests passing through the gateway are performed using the credentials of the gateway. This practice eliminates the need to maintain duplicate security databases on both the BEA Tuxedo and BEA TOP END systems.
Mutual authentication of the BEA TOP END and TEDG nodes and encryption of messages between nodes is optional. These capabilities, based on the BEA TOP END security algorithms, use the BEA TOP END security package.

The following illustration shows how security works between BEA Tuxedo and BEA TOP END systems. For more detailed information, see:

back to top

previous page

next page

Copyright © 2001 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.