You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UAA integration of Kibana works well for non-admin except it allows Management Menu.
If a user is a OrgOwner (non-system org), Kibana nicely filters firehose data to show only what they should see. However the "Management Menu" option (left side of Kibana screen) is accessible and allows a user to modify critical Kibana configuration items.
Can the Management menu be configured to only allow UAA users that are part of the "system" org to access?
The text was updated successfully, but these errors were encountered:
--
Regards,
Andrei
28 февр. 2018 г., 0:44 +0300, Kurt Kellner <[email protected]>, писал:
UAA integration of Kibana works well for non-admin except it allows Management Menu.
If a user is a OrgOwner (non-system org), Kibana nicely filters firehose data to show only what they should see. However the "Management Menu" option (left side of Kibana screen) is accessible and allows a user to modify critical Kibana configuration items.
Can the Management menu be configured to only allow UAA users that are part of the "system" org to access?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
UAA integration of Kibana works well for non-admin except it allows Management Menu.
If a user is a OrgOwner (non-system org), Kibana nicely filters firehose data to show only what they should see. However the "Management Menu" option (left side of Kibana screen) is accessible and allows a user to modify critical Kibana configuration items.
Can the Management menu be configured to only allow UAA users that are part of the "system" org to access?
The text was updated successfully, but these errors were encountered: