About CMP Role-Based Security

CMPClosed Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. employs a multi-level role-based security model in which each userClosed A person with the capability to log in to the CMP GUI software, such as a customer service advisor or agent. who has rights to access a CMP component is assigned zero or more roles that define which functional area or resource they can access once they are successfully authenticated. Roles can give access to:

Roles are organised in a hierarchy:

Example

Suppose user JoeSmith has three group roles assigned:

  • Everybody
  • Consumer User
  • BackOffice

For the purposes of this example, the Everybody role is not extended any further, but the Consumer User and BackOffice groups each have parent roles assigned. Both groups have an Agent View Application role that allows access to an application and is not extended any further - that is, it has no child roles assigned to it. However, the two groups also have parent roles:

  • Consumer User has the parent role View Customer Data.
  • BackOffice has the parent role Problem Resolution and Comms.

Each of these parent groups has a number of roles assigned as children. For example, the Comms parent role has the following child roles:

  • Maintain Communications.
  • Send Communications.
  • View Communications.

The hierarchy of group, parent and child roles is as follows:

From a CMP perspective, the list of roles associated with the JoeSmith are those coloured teal in the diagram.

Groups are controlled by the Identity Server. The relationship between groups and roles is defined by the role-extender service. For more information, see Security Technical Architecture.