Update get token response to include auth info #5378
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mpdreamz
requested changes
Mar 2, 2021
src/Nest/XPack/Security/User/GetUserAccessToken/GetUserAccessTokenResponse.cs
Outdated
Show resolved
Hide resolved
stevejgordon
force-pushed
the
feature/auth-info-get-token-response
branch
from
c46f54a to
711b326
Compare
github-actions bot
pushed a commit
that referenced
this pull request
Mar 3, 2021
* Update get token response to include auth info * Update token response * Update response
github-actions bot
pushed a commit
that referenced
this pull request
Mar 3, 2021
* Update get token response to include auth info * Update token response * Update response
stevejgordon
added a commit
that referenced
this pull request
Mar 5, 2021
stevejgordon
added a commit
that referenced
this pull request
Mar 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the response as a result of this enhancement - elastic/elasticsearch#62490
I've taken a similar approach as the server-side implementation by reusing the
AuthenticateResponsetype.