[FIX] Ensure that the accessToken is set back to the original #547
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
…t ever it was set too, prior to Revoking any other AccessTokens.
davidcollom
requested review from
EduardoVV,
luispresuelVenafi,
marcos-albornoz and
rvelaVenafi
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
… (or whatever it was set too, before Revoking any other AccessTokens.
While the intended behaviour is that the
RevokeAccessTokenAPI Call uses the Access Token we want to Revoke, we also don't want to remove any valid access tokens we may already have setup within the vCert Client.