Skip to content

Conversation

@cjcenizal
Copy link
Contributor

These are the privileges required for a user to access both remote clusters and CCR:

image

If you log in as a user without those permissions (e.g. a user with only the kibana_user role), CCR will look like this:

image

This PR displays the title to keep CCR consistent with RC and Rollup Jobs:

image

image

image

@cjcenizal cjcenizal added Feature:CCR and Remote Clusters Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t// labels Dec 15, 2018
@cjcenizal cjcenizal requested a review from sebelga December 15, 2018 01:13
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@cjcenizal cjcenizal requested a review from jen-huang December 17, 2018 18:44
Copy link
Contributor

@sebelga sebelga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM! I haven't been able to test it in the browser as I don't know what Kibana user is needed to manage privileges.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nit: this could be simply written: {isAutoFollowApiAuthorized && ( ... without the ternary operator

@cjcenizal cjcenizal force-pushed the ccr/show-header-when-unauthorized branch from a2811e5 to a5786fc Compare December 18, 2018 17:23
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@cjcenizal cjcenizal merged commit 3a2841b into elastic:feature/ccr Dec 18, 2018
@cjcenizal cjcenizal deleted the ccr/show-header-when-unauthorized branch December 18, 2018 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature:CCR and Remote Clusters Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more t//

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants