Perform OAuth flow in same window #22
Merged
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.
This part is actually quite simple. I had to rearrange some of my application to cope with the different workflow.
I created an endpoint in my app,
/oauth/callback
, and anOAuthCallbackController
to handle it. Then I created a simple HTML file for my redirect URI, similar tooauth2callback.html
but instead of loading Angular, it simply manipulates the URL to make it compatible with "hashbang" routing and pass it along to the Angular endpoint:Then I'm able to access the OAuth params from my controller, set the token and all that good stuff: