Configuring a default systems administrator for Cloudera Observability On-Premises
Pre-tasks that are required before you can start enabling role based access in Cloudera Observability On-Premises.
Describes how to enable role based access in Cloudera Observability On-Premises and configure a
Cloudera Observability On-Premises default systems administrator.
Before you can assign
access roles in Cloudera Observability On-Premises you must first enable role based access and
configure a default systems administrator. Both tasks are completed in Cloudera
Manager. Once configured, the default administrator (also known as a superuser) can
log into the Cloudera Observability On-Premises UI and assign the System Admin access policy
role to one or more users.
In a supported web browser on the Cloudera Observability On-Premises on-premises cluster,
log in to Cloudera Manager.
In Cloudera Manager, select Clusters,
OBSERVABILITY, and then click the
Configuration tab.
In the Configuration page, search for the Role Based Access
enabled property and then select its OBSERVABILITY
(Service-Wide) check box.
According to your requirements, do one of the following:
In the OBSERVABILITY (Service Wide) field of the
OBSERVABILITY Default Super Users property,
enter either the user name or the account name of a system administrator
who is to be granted access to perform administration tasks in Cloudera Observability On-Premises. By default, admin.
In the OBSERVABILITY (Service Wide) field of the
OBSERVABILITY Default Super Groups property,
enter the group account name of your LDAP admin group. For example,
admin_grp.
The following image shows the configuration properties:
Click Save Changes.
Navigate to the top of the Cloudera Observability On-Premises service page and from the
Actions menu, restart the Cloudera Observability On-Premises
service, by selecting Restart.