We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When we first create a new user with security plugin from API
curl -XPUT "http://localhost:9200/_plugins/_security/api/internalusers/<username>" -H 'Content-Type: application/json' -d' { "password": "kirkpass", "opendistro_security_roles": ["maintenance_staff", "database_manager"], "backend_roles": ["role 1", "role 2"], "attributes": { "attribute1": "value1", "attribute2": "value2" } } '
the response status is 201 with context message like
201
{ "status":"CREATED", "message":"User kirk created" }
However, the spec doesn't have such response.
opensearch-api-specification/spec/namespaces/security.yaml
Lines 615 to 617 in 9df46f8
Run the command above and retrieve the response status.
There should be a response of 201 for PUT /_plugins/_security/api/internalusers/{username}.
PUT /_plugins/_security/api/internalusers/{username}
The text was updated successfully, but these errors were encountered:
Found this issue when I run the smoke tests from opensearch-build repo when onboarding security plugin into the test framework.
Sorry, something went wrong.
Want to try to contribute this @zelinh?
zelinh
Successfully merging a pull request may close this issue.
What is the bug?
When we first create a new user with security plugin from API
the response status is
201
with context message likeHowever, the spec doesn't have such response.
opensearch-api-specification/spec/namespaces/security.yaml
Lines 615 to 617 in 9df46f8
How can one reproduce the bug?
Run the command above and retrieve the response status.
What is the expected behavior?
There should be a response of
201
forPUT /_plugins/_security/api/internalusers/{username}
.The text was updated successfully, but these errors were encountered: