Configuring TEDG-to-NI Encryption and Authentication


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Doc Home \| TOP END Domain Gateway \| Topic List \| Previous \| Next \| Contents

Using the BEA Tuxedo TOP END Domain Gateway

If, in the DMCONFIG file, you have assigned a value other than NONE to the SECURITY parameter, then you must establish mutual authentication and encryption. To do so, complete the following procedure.

In the BEA TOP END security database, define a Kerberos principle of the form node.system for each node (machine) running the TEDG. The value of node is the name of the machine; the value of system is the name of the BEA TOP END system. (On a UNIX system, you can obtain the name of the machine by running the uname -n command.)
Generate a Kerberos SRVTAB file for each node and make all such files available to each TEDG at start of day. These files are needed by the TEDG when a security level (CLEAR, SAFE, or PRIVATE) is configured in the DMCONFIG file.
For each principle, create a SRVTAB file by using the ext_srvtab(1T) utility on the Kerberos master node. Rename each file as srvtab.system, where the value of system is the BEA TOP END system name of the principle.
Copy each file to the appropriate directory (defined by the APPDIR environment variable) on the TEDG node.