OAuth how to test with local URLs

Question

I am trying to test OAuth buttons  but they all  Facebook  Twitter  LinkedIn  come back with errors that seem to signal that I can not test or use them from a local URL   How do people usually work in development with OAuth stuff if they all seem to require a non-dev and non-local connections environments

User · Answer

I found xip io which automatically converts a fixed url to a embedded localhost domain  For example lets say your localhost server is running on 127 0 0 1 8000 You can go to http   www 127 0 0 1 xip io 5555  to access this server  You can then add this address to Oauth configuration for Facebook or Google

User · Answer

You can edit the hosts file on windows or linux  Windows   C  Windows System32 Drivers etc hosts Linux    etc hosts     localhost name resolution is handled within DNS itself       127 0 0 1       mywebsite com   after you finish your tests you just comment the line you add to disable it     127 0 0 1       mywebsite com

User · Answer

For Mac users  edit the  etc hosts file  You have to use sudo vi  etc hosts if its read-only  After authorization  the oauth server sends the callback URL  and since that callback URL is rendered on your local browser  the local DNS setting will work   127 0 0 1       mylocal com

User · Answer

Taking Google OAuth as reference   In your OAuth client Tab    Add your App URI example http   localhost 3000  to Authorized JavaScript origins  URIs  In your OAuth consent screen    Add mywebsite com to Authorized domains  Edit the hosts file on windows or linux Windows C  Windows System32 Drivers etc hosts Linux    etc hosts to add 127 0 0 1 mywebsite com   N B  Comment out any if there is any other 127 0 0 1

User · Answer

Another valuable option would be https   github com ThomasMcDonald Localhost-uri-Redirector  It s a very simple html page that redirects to whatever host and port you configure in the UI  The page is hosted on Github https   thomasmcdonald github io Localhost-uri-Redirector  so you can use that as your OAuth2 redirect url and configure you target host and port in the UI and it will just redirect to your app

User · Answer

Or you can use https   tolocalhost com  and configure how it should redirect a callback to your local site  You can specify the hostname  if different from localhost  i e  yourapp local and the port number   For development purposes only

User · Answer

Set your local domain to mywebsite example com  and redirect it to localhost  -- even though the usual is to use mywebsite dev  This will allow robust automatic testing  Although authorizing  test and  dev is not allowed  authorizing example com is allowed in google oauth2   You can redirect any domain to localhost in your hosts file  unix linux   etc hosts   Why mywebsite example com  Because example com is a reserved domain name  So  there would be no naming conflicts on your machine  no data-risk if your test system exposes data to not-redirected-by-mistake example com

User · Answer

You can also use ngrok  https   ngrok com   I use it all the time to have a public server running on my localhost  Hope this helps   Another options which even provides your own custom domain for free are serveo net and https   localtunnel github io www

User · Answer

Google doesn t  allow test auth api on localhost using http   webporject dev or  loc and  etc and  google short link that shortened your local url http   webporject dev  also bit ly     Google accepts only url which starts http   localhost      if you want to test google auth api you should follow these steps        if you use openserver go to settings panel and click on aliases tab and click on dropdown then find localhost and  choose it   now you should choose your local web project root folder by clicking the next dropdown that is next to first dropdown   and click on a button called add and restart opensever   now your local project available on this link http   localhost  also you can paste this local url to google auth api to redirect url field

User · Answer

Update October 2016  Easiest now  use lvh me which always points to 127 0 0 1  Previous Answer  Since the callback request is issued by the browser  as a HTTP redirect response  you can set up your  hosts file or equivalent to point a domain that is not localhost to 127 0 0 1  Say for example you register the following callback with Twitter  http   www publicdomain com callback   Make sure that www publicdomain com points to 127 0 0 1 in your hosts file  AND that twitter can do a successful DNS lookup on www publicdomain com  i e the domain needs to exist and the specific callback should probably return a 200 status message if requested  EDIT  I just read the following article  http   www tonyamoyal com 2009 08 17 how-to-quickly-set-up-a-test-for-twitter-oauth-authentication-from-your-local-machine  which was linked to from this question  Twitter oAuth callbackUrl - localhost development  To quote the article   You can use bit ly  a URL shortening service  Just shorten the  localhost URL such as http  localhost 8080 twitter callback  and register the shortened URL as the callback in your Twitter app   This should be easier than fiddling around in the  hosts file  Note that now  Aug  14  bit ly is not allowing link forwarding to localhost  however Google link shortener works  PS edit   Nov  18   Google link shortener stopped giving support for localhost or 127 0 0 1

[oauth] OAuth: how to test with local URLs?

Examples related to oauth

Examples related to localhost