Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.11] Fix custom branding for users without "Saved Object Management…
…" privilege (elastic#171308) (elastic#171530) # Backport This will backport the following commits from `main` to `8.11`: - [Fix custom branding for users without "Saved Object Management" privilege (elastic#171308)](elastic#171308) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Anton Dosov","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-11-20T12:36:21Z","message":"Fix custom branding for users without \"Saved Object Management\" privilege (elastic#171308)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/163842\r\n\r\nCurrently, Saved Objects Management Kibana privilege ( either read or\r\nall) is needed in order for a user to see custom branding. Without it,\r\nusers with custom roles see the default branding after logging in.\r\n\r\nCustom branding is stored in the new \"global\" advanced settings\r\n(\"config-global\" saved object). Only users with Saved Objects Management\r\nprivilege had access to it. This PR adds \"config-global\" to the list of\r\nautomatically applied privileges similar to \"config\".","sha":"385fe054ffc3c7c85d0a887ff106aae6b1ec6d75","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:SharedUX","backport:prev-minor","v8.12.0"],"number":171308,"url":"https://github.com/elastic/kibana/pull/171308","mergeCommit":{"message":"Fix custom branding for users without \"Saved Object Management\" privilege (elastic#171308)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/163842\r\n\r\nCurrently, Saved Objects Management Kibana privilege ( either read or\r\nall) is needed in order for a user to see custom branding. Without it,\r\nusers with custom roles see the default branding after logging in.\r\n\r\nCustom branding is stored in the new \"global\" advanced settings\r\n(\"config-global\" saved object). Only users with Saved Objects Management\r\nprivilege had access to it. This PR adds \"config-global\" to the list of\r\nautomatically applied privileges similar to \"config\".","sha":"385fe054ffc3c7c85d0a887ff106aae6b1ec6d75"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171308","number":171308,"mergeCommit":{"message":"Fix custom branding for users without \"Saved Object Management\" privilege (elastic#171308)\n\n## Summary\r\n\r\nfix https://github.com/elastic/kibana/issues/163842\r\n\r\nCurrently, Saved Objects Management Kibana privilege ( either read or\r\nall) is needed in order for a user to see custom branding. Without it,\r\nusers with custom roles see the default branding after logging in.\r\n\r\nCustom branding is stored in the new \"global\" advanced settings\r\n(\"config-global\" saved object). Only users with Saved Objects Management\r\nprivilege had access to it. This PR adds \"config-global\" to the list of\r\nautomatically applied privileges similar to \"config\".","sha":"385fe054ffc3c7c85d0a887ff106aae6b1ec6d75"}}]}] BACKPORT--> Co-authored-by: Anton Dosov <[email protected]>
- Loading branch information