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

Fixing a problem with potential dirty read of a token document on token refresh #64031

Merged
merged 5 commits into from
Oct 26, 2020

Conversation

BigPandaToo
Copy link
Contributor

As discussed in (#55816) #55816 (comment)
Related to #59685

@ywangd
Copy link
Member

ywangd commented Oct 22, 2020

Could you please add @jkakavas as a reviewer as well since he knows more about this part of code? Thanks

Adding CreateTokenResult to hold authentication object
@BigPandaToo
Copy link
Contributor Author

@elasticmachine update branch

Copy link
Member

@ywangd ywangd left a comment

Choose a reason for hiding this comment

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

LGTM. I left a comment for discussion if anyone is interested.

@BigPandaToo
Copy link
Contributor Author

@elasticmachine update branch

@BigPandaToo BigPandaToo merged commit c23c057 into elastic:master Oct 26, 2020
BigPandaToo added a commit to BigPandaToo/elasticsearch that referenced this pull request Oct 26, 2020
…en refresh (elastic#64031)

* Fixing a problem with potential dirty read of a token document.
Related to elastic#59685

* Fixing a problem with potential dirty read of a token document.
Adding CreateTokenResult to hold authentication object

* Fixing a problem with potential dirty read of a token document.
Adding CreateTokenResult to hold authentication object

Co-authored-by: Elastic Machine <[email protected]>
BigPandaToo added a commit that referenced this pull request Oct 26, 2020
…en refresh (#64031) (#64178)

* Fixing a problem with potential dirty read of a token document on token refresh (#64031)

* Fixing a problem with potential dirty read of a token document.
Related to #59685

* Fixing a problem with potential dirty read of a token document.
Adding CreateTokenResult to hold authentication object

* Fixing a problem with potential dirty read of a token document.
Adding CreateTokenResult to hold authentication object

Co-authored-by: Elastic Machine <[email protected]>

* Fixing tests failures

Co-authored-by: Elastic Machine <[email protected]>
@ywangd
Copy link
Member

ywangd commented Oct 28, 2020

Hi @BigPandaToo Not sure if you have talked to @jkakavas, often times we would wait for approvals from all requested reviewers before merging a PR. It's not a requirement, I think our team just kinda spontaneously got into and settled on this habit.

@BigPandaToo
Copy link
Contributor Author

@ywangd Yes, we talked. I thought one LGTM is enough. Will know.

tvernum added a commit that referenced this pull request Oct 30, 2020
Rebasing #64259 on top of #64031 introduced a test compile error, but
it looks like PR-CI failed to run the correct set of checks so the PR
was green and was merged.

This change fixes those compile issues.
@ywangd ywangd added >non-issue :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) and removed >bug labels Jan 4, 2021
@BigPandaToo BigPandaToo deleted the FixRefreshTokenResponse branch April 19, 2021 13:49
@jakelandis jakelandis removed the v8.0.0 label Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>non-issue :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team v7.11.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants