APIs use credential-based authentication. You must have a valid user ID and password to access APIs.
To control access to APIs, Administrators create accounts that have a user name, a role, and an associated password.
The role defines the level of access granted to users under that account. BMC Real End User Experience Monitoring Software Edition offers the following predefined roles: User roles and access permissions User role Description Provides access to sensitive configurations, such as private key management, enabling and disabling the transaction capture, and configuring data confidentiality policies. The Security role is given to a system administrator, who could perform the following tasks: Provides access to all features that the Administrator role has except for account management. This role exists for device and data management purposes. The Operator or Observer role is given to application support personnel or application developers, who could perform the following tasks: In BMC Application Diagnostics, the Observer role is the same as the Operator role. When integrated with BMC Real End User Experience Monitoring, the Observer role provides access to the web interface, but users with this role cannot make any configuration changes other than to save query settings. The permissions of this role are sufficient to perform day-to-day tasks.Security Administrator Provides access to all functions of the system that are not related to security. This role exists primarily for account management purposes. Operator Observer Export Provides no access to the web interface and is limited to downloading data via data export APIs.
Roles and permissions matrix
Permission →
| Security | Accounts | Overall | Web | Data |
---|---|---|---|---|---|
Security | • | • | • | • | • |
Administrator |
| • | • | • | • |
Operator |
|
| • | • | • |
Observer |
|
|
| • | • |
Export |
|
|
|
| • |