Why did github make their OAuth so bad?

Question

GitHub

I do registration \ authorization \ connection of a github account to a local one on passport.js/
BUT for registration \ authorization I need one callback, and for linking an account I need another.
Everything went smoothly with FB and VK when I specified callbacks in the config, but github ignores my configs about it and in any case redirects to the callback specified in the form: You

can’t leave the field empty, someone knows how to specify your callbacks in your config ?

Answer 1

Nothing, until GitHub itself changes it :)
For test applications, I made a web proxy:
oauthproxy.nemiro.net
The JavaScript code can be viewed on the page.
There, a redirect is made to the address specified in returnUrl .
This does not work for all vendors, there are more restrictions, but GitHub quite allows you to use this trick.
For some vendors, you have to create a bunch of applications for each callback address :)
I made a pivot table (not published yet) for one article. A snapshot of the table is presented below, it may be useful: The
information is current as of December 2014.