Changing a security model

A security model is always applied in TrueSight Middleware Administrator. Security policies in-place dictates use of a particular model out of the five available.

Changing a security model is meant to be a rare occurrence in TrueSight Middleware Administrator. Because of the risk of potential loss of application work, we recommend a security model change be a one-time procedure. Make sure to read all directions in this section before changing a model.

Note that the Security object is not fully supported in TrueSight Middleware Administrator (Monitor Edition). For example, Product Administrators can modify LDAP_LDAP security settings to accommodate changes in their LDAP environment, but cannot change the security model.

See a summary of the functionality differences between the full version of TrueSight Middleware Administrator and TrueSight Middleware Administrator (Monitor Edition).

Please do not add projects, connections or other key system components before changing a security model. If a new security model is applied that uses a different authorization method, users and groups may disappear from projects. It is highly recommended that you change models immediately after installation.

Changing a model

To change a current security model, follow the instructions below. They assume that you have opened the application and navigated to the Administration Console.

Note that these instructions assume change to a model that includes LDAP for either the authentication or the authorization portion of the security model you have chosen to replace the current one.

  1. Select Security from the Navigation Panel, and then select the relevant Security Model from the drop-down menu. Refer to Steps 4 to 9 in the Implementing-the-LDAP_LDAP-model section for further details.
  2. Verify that the change has gone smoothly. Refer to Testing-a-new-security-model to confirm success.

 

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