Skip to content
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] Fix clarity of 7.6 derived key breaking change #60154

Merged
merged 1 commit into from
Jul 27, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/reference/migration/migrate_7_6.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,8 @@ privileges for the API key. Previously, when you created a derived key, it had
no privileges. This behavior disregarded any privileges that you specified in
the {ref}/security-api-create-api-key.html[create API key API].

As of 7.6.2, this behavior changes. To create derived keys with no privileges,
you must explicitly specify an empty role descriptor. For example:
As of 7.6.2, this behavior changes. To create a derived key, you must explicitly
specify a role descriptor with no privileges:

[source,js]
----
Expand Down