Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see MainView Middleware Monitor 9.2.

User authentication and permissions


The MainView Middleware Monitor (MVMM) product supports the following authentication modes: 

  • Internal Security – local authentication that uses the distributed directory information service
  • Active Directory Delegate Mode – combines Active Directory Authentication (user identification and password checking) and Internal LDAP authorization

The MVMM product uses LDAP as the underlying security protocol for all user authentication. All references to LDAP in the documentation refer to the underlying security method and not an external LDAP directory service, otherwise known as a Directory System Agent. Connecting to a Directory System Agent is not supported.

Related topics

Changing-default-passwords 

Defining-user-access-and-security-settings

Configuring-Active-Directory-security

Users, user groups, and permissions

Regardless of your user authentication mode, user permission is handled using the concept of user groups. A user is a member of at least one user group. Permissions are granted to the groups and, by extension, to the members of the group.
All users in a group have identical permissions. Changes applied to one user in a group are applied to all user in the group. Users can be added to and removed from groups as required.

A user can belong to more than one group. When a user belongs to groups with different permissions, the user is granted the union of all permissions.

Once the type of security has been chosen, either Internal (default) or Active Directory, you should not switch from one to the other even if you run the Security Configuration Tool again. When Active Directory is chosen and working, you should not switch to another Active Directory unless it has the same groups.

If you need to change the type of security or switch to a different Active Directory with a different directory of groups, contact BMC support for advice on how to do this. Changing the directory of groups affects both MainView Middleware Monitor and MainView Middleware Administrator, regardless of its edition.

Internal Security mode

User authenticated is handled by an internal Apache Directory Server. 

Active Directory Delegate Mode


Active Directory Delegate Mode Security allows for configuring MainView Middleware Monitor security to authenticate a user via their Active Directory credentials and group memberships while allowing for MainView Middleware Monitor user and group authorization and configuration information to be stored in its internal database.

This mode alleviates the need to modify the Active Directory schema. It might require the Active Directory administrator to set up Groups and User associations that are used to dictate a user's level of authority. Internal users (such as TopicService, etc.) are maintained in the internal MainView Middleware Monitor database, and are not required in the Active Directory domain.

You can configure Active Directory Delegate Mode security either automatically with the securityconfig tool (the recommended method), or manually by modifying the services.cfg file.

In MainView Middleware Monitor, access permission is granted at a group level. Members of the group inherit all permissions granted to the group. Changes to a group's permissions are applied to all users in the group. Users in more than one group inherit the union of permissions from all the groups in which they are members.

Note

Users have no access rights until they are members of at least one group.

If you use Active Directory security, contact your Active Directory administrator for assistance. Note that the "ADS" mode of integration with Microsoft Active Directory is not supported.

See also Configuring Active Directory security.

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

MainView Middleware Monitor security enables you to create user accounts and security groups to manage user access to MainView Middleware Monitorfunctionality. For a full review of the security options, see the Administering section.



 

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