-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOCS][skip ci] Adjusting production setup instructions as a result of Spaces/RBAC #36890
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kobelb
added
Team:Docs
v8.0.0
release_note:skip
Skip the PR/issue when compiling release notes
v7.2.0
labels
May 22, 2019
Pinging @elastic/kibana-docs |
kobelb
commented
May 22, 2019
|
||
For information about setting up Kibana users, see | ||
{kibana-ref}/using-kibana-with-security.html[Configuring security in Kibana]. | ||
For more information on granting access to Kibana, see <<xpack-security-authorization>>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once #35656 merges, this link will be ever better!
legrego
reviewed
May 22, 2019
Co-Authored-By: Larry Gregory <lgregorydev@gmail.com>
legrego
approved these changes
May 22, 2019
💔 Build Failed |
kobelb
changed the title
[DOCS] Adjusting production setup instructions as a result of Spaces/RBAC
[DOCS][skip ci] Adjusting production setup instructions as a result of Spaces/RBAC
May 22, 2019
kobelb
added a commit
to kobelb/kibana
that referenced
this pull request
May 22, 2019
…f Spaces/RBAC (elastic#36890) * Adjusting production setup instructions as a result of Spaces/RBAC * Update docs/setup/production.asciidoc Co-Authored-By: Larry Gregory <lgregorydev@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to these changes, we were recommending assigning the
kibana_user
role to grant access to Kibana. While this is "fine" we don't want to do so in all scenarios.Additionally, we were stating that there is no way to control which users have access to which Dashboards, which is just false after Larry's Awesome Spaces.