-
Notifications
You must be signed in to change notification settings - Fork 256
[DOCS] Replaces X-Pack security terminology #187
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
Conversation
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.
I left a couple of suggestions
Authorization is the process of determining whether the user behind an incoming | ||
request is allowed to execute the request. | ||
The {stack-security-features} introduce the concept of _authorization_ to the | ||
{stack}. Authorization is the process of determining whether the user behind an |
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.
The repeated use of "stack" feels a little off. We may need to phrase this quite differently if we to avoid describing {security} as being something extra that's added to the stack.
Maybe:
The {stack-security-features} include support for the concept of _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.
Thanks @tvernum , I change it to: "The {stack-security-features} add authorization, which is the process of determining whether the user..."
Related to elastic/docs#407
This PR replaces occurrences of {security} or "X-Pack Security" with the new {security-features}, {stack-security-features}, or {es-security-features} terminology.