After performing an OAuth login, Goat Guardian will forward the end-user to the URL specified by the upstream web application (as described in #25).
When forwarding the end-user, Goat Guardian should include the parameters from the OAuth token for the user.
For instance, when logging in with Twitter, the OAuth token contains the following information:
twitter user ID
twitter user screen name
This information should be sent to the upstream web application as a URL parameter.
For instance, if the redirect URL is specified as http://localhost:3000/some/path, then Goat Guardian should actually redirect the user to a URL like http://localhost:3000/some/path?provider=twitter&twitter_user_id=1234567890&twitter_screen_name=realDonaldTrump.
This way the upstream web application can see the user's twitter ID.
After performing an OAuth login, Goat Guardian will forward the end-user to the URL specified by the upstream web application (as described in #25).
When forwarding the end-user, Goat Guardian should include the parameters from the OAuth token for the user.
For instance, when logging in with Twitter, the OAuth token contains the following information:
This information should be sent to the upstream web application as a URL parameter.
For instance, if the redirect URL is specified as
http://localhost:3000/some/path, then Goat Guardian should actually redirect the user to a URL likehttp://localhost:3000/some/path?provider=twitter&twitter_user_id=1234567890&twitter_screen_name=realDonaldTrump.This way the upstream web application can see the user's twitter ID.