Specifying the Security Level


	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 \| Setting Up a BEA Tuxedo Application \| Local Topics \| Previous Topic \| Next Topic \| Contents

Specifying the Security Level

You can set the following three levels of security:

PERM parameter—provides minimal security by restricting, through permissions, the ability to write to the application queues.
SECURITY parameter—provides greater security. When this parameter is set, a client must supply a password when joining the application. This password is checked against the password supplied by the administrator when the TUXCONFIG file is generated from the UBBCONFIG file.
AUTHSVC parameter—sets the maximum level of security. When this parameter is set, any client request to join the application is sent to an authentication service. The authentication service may be the default service supplied by the BEA Tuxedo system or a third-party vendor service, such as a Kerberos service. This level of security cannot be used unless the SECURITY parameter is set.

Characteristics of the SECURITY and AUTHSVC Parameters

Parameter	Characteristics
SECURITY	Security level that requires a password to join an application. Accepted values are: NONE (default), APP_PW, USER_AUTH—>ACL, and MANDATORY_ACL. Default is NONE. Example: SECURITY APP_PW
AUTHSVC	The name of the authentication service. SECURITY APP_PW or higher must be specified. Default is no authentication service. Client authentication with Kerberos is possible. Example: AUTHSVC "AUTHSVC''

See Also

Introducing ATMI Security in Using Security in ATMI Applications
Using Security in CORBA Applications

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.