Skip to content

Security: remove wrapping in put user response#33512

Merged
jaymode merged 4 commits intoelastic:masterfrom
jaymode:put_user_rest_response
Sep 13, 2018
Merged

Security: remove wrapping in put user response#33512
jaymode merged 4 commits intoelastic:masterfrom
jaymode:put_user_rest_response

Conversation

@jaymode
Copy link
Copy Markdown
Member

@jaymode jaymode commented Sep 7, 2018

This change removes the wrapping of the created field in the put user
response. The created field was added as a top level field in #32332,
while also still being wrapped within the user object of the
response. Since the value is available in both formats in 6.x, we can
remove the wrapped version for 7.0.

This change removes the wrapping of the created field in the put user
response. The created field was added as a top level field in elastic#32332,
while also still being wrapped within the `user` object of the
response. Since the value is available in both formats in 6.x, we can
remove the wrapped version for 7.0.
@jaymode jaymode added >enhancement >breaking v7.0.0 :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) labels Sep 7, 2018
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-security

@jaymode
Copy link
Copy Markdown
Member Author

jaymode commented Sep 7, 2018

run the java11 tests

Copy link
Copy Markdown
Contributor

@albertzaharovits albertzaharovits left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK Thanks!

@jaymode jaymode merged commit 3914a98 into elastic:master Sep 13, 2018
@jaymode jaymode deleted the put_user_rest_response branch September 13, 2018 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>breaking >enhancement :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) v7.0.0-beta1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants