Product security mechanisms


Basic security components are logon [authentication], and users/groups management [authorization]. The assignment of user permissions is another element of the authorization mechanism. The Product Administrator is always responsible for assigning permissions to users and groups for associated projects.

Various security models exist in TrueSight Middleware Administrator. Each model handles product security uniquely; each offers a different combination of authentication and authorization methods to implement security.

The security models let the Product Administrator implement authentication and authorization in different ways:

  • Implement all security components within the product space. In practice, this typically means mapping information to product-specific or product-internal records or databases and doing authentication and authorization from there.
  • Uses external sources and means to perform authentication while keeping authorization within the bounds of TrueSight Middleware Administrator.
  • Assign both authentication and authorization tasks to an external source.

The user is shielded from this mechanism and the set of security implementations expressed in the security models. No functional options or requirements exist for the user in relation to security.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC TrueSight Middleware Administrator 8.2