In our OAuth1, after the user clicked 'Allow' in the browser, the user would get a 'success' message.
In our OAuth2, the 'Allow' page in the browser just sits there (even though the app has authenticated and gotten the token). Eventually it times out and says:
"Hmm, we can't reach this page."
It seems to me that somehow that browser should get updated to say 'success'.
I've implemented a localhost server on the specified port and it is getting the returned authorization code. Do I need to post something back to let the browser know everything is ******, dumb and happy? If so, what?