-
Notifications
You must be signed in to change notification settings - Fork 246
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
New Java client does not have all fields for CreateApiKeyRequest.RoleDescriptor #106
Comments
Pinging @elastic/es-data-management (Team:Data Management) |
I think this is actually a documentation error. The page https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-create-api-key.html describes the field
According to service specification the structure of those role descriptor are not the same. Also the example on the same page uses |
The API specification is actually wrong, and these are the same structure. Elasticsearch accepts both elastic/elasticsearch-specification#1555 has been opened to solve this, and the Java client will be updated once it's fixed. |
Elasticsearch version (
bin/elasticsearch --version
):7.16.2
Plugins installed: []
JVM version (
java -version
):openjdk 17
OS version (
uname -a
if on a Unix-like system):not relevant
Description of the problem including expected versus actual behavior:
The description in https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-put-role.html mentions fields like
indices
,global
andrun_as
which are not defined in the Java clientThey are also not defined in the service specification.
However, the are defined in the elasticsearch-rest-high-level-client.
I am using the wrong Java API to create an api key? Or should the spec and/or docs be updated?
Steps to reproduce:
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: