BEA Logo BEA Tuxedo Release 8.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

   Tuxedo Documentation   |   Using Security in ATMI Applications   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents

 


ATMI Security Capabilities

The BEA Tuxedo system can enforce security in a number of ways, which includes using the security features of the host operating system to control access to files, directories, and system resources. The following table describes the security capabilities available with the ATMI environment of the BEA Tuxedo product.

ATMI Security Capabilities

Security Capability

Description

Plug-in Interface

Default Implementation

Operating system security

Controls access to files, directories, and system resources.

N/A

N/A

Authentication

Proves the stated identity of users or system processes; safely remembers and transports identity information; and makes identity information available when needed.

Implemented as a single interface

The default authentication plug-in provides security at three levels: no authentication, application password, and user-level authentication. This plug-in works the same way the BEA Tuxedo implementation of authentication has worked since it was first made available with the BEA Tuxedo system.

Authorization

Controls access to resources based on identity or other information.

Implemented as a single interface

The default authorization plug-in provides security at two levels: optional access control lists and mandatory access control lists. This plug-in works the same way the BEA Tuxedo implementation of authorization has worked since it was first made available with the BEA Tuxedo system.

Auditing

Safely collects, stores, and distributes information about operating requests and their outcomes.

Implemented as a single interface

Default auditing security is implemented by the BEA Tuxedo EventBroker and user log (ULOG) features.

Link-level encryption

Uses symmetric key encryption to establish data privacy for messages moving over the network links that connect the machines in an ATMI application.

N/A

RC4 symmetric key encryption.

Public key security

Uses public key (or asymmetric key) encryption to establish end-to-end digital signing and data privacy between ATMI application clients and servers. Complies with the PKCS-7 standard.

Implemented as six interfaces

Default public key security supports the following algorithms:

See Also

 

back to top   next page