Feature: Obtain tokens using authorization code flow using ESTSAuth cookie #9
Conversation
This file contains 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
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.
I should have just consolidated this and the previous PR 😆
Introduces alternative method to device code flow for obtaining tokens. Given an
ESTSAuthorESTSAuthPersistentcookie, obtained via AitM phishing or other cookie theft methods, we can use the Authorization Code flow to get a refresh token ("code") for a FOCI application (by default: Teams).This exchange method was implemented using Selenium in roadtx; I have not yet encountered a scenario where user interaction is actually required if a valid cookie is presented and it seems to work just fine using Invoke-RestMethod/invoke-WebRequest calls.