Skip to main content
Best answer

Weird behavior while testing OAuth


Hey! 

Im trying to setup OAuthV2 for Zapier Authentication. But have not been able to test it within the console, when I click “Sign in to <your_integration_name>” a popup window opens and the resulting URL looks something like https://zapier.comhttps//localhost:3000/api/oauth/authorize?client_id=qJWKiVUN4zx8Ws1x3XzKTBmRownUD-FK&state=1596745737.868160554912&redirect_uri=https%3A%2F%2Fzapier.com%2Fdashboard%2Fauth%2Foauth%2Freturn%2FApp114171CLIAPI%2F&response_type=code
and the browser obviously complains

Any suggestion here? I already tried using a different domain like “mydomain.com” but the problems seems to rely on how the Console handles the popup thing

 



 

Best answer by ditorojuanfBest answer by ditorojuanf

avid.aml wrote:

+1 This problem is plaguing me too. I can’t get past first base in creating my app. I am using Auth0 as the OAuth2 provider so my authentication URL is different to the OP’s but I see the exact same problem: the URL is prepended with https://zapier.com resulting in an invalid URL so fails on DNS.


seems that this​​​​​​ is fixed now 

However you can do the flow manually, just remove the zapier.comhttps// part from the URL and start the flow from there, once you have a successful response just refresh the Platform UI(web console) page and on the testing bit you will see you are authenticated and just click on “Test Authentication” to validate that your /me endpoint works fine

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

5 replies

  • New
  • 3 replies
  • August 7, 2020

+1 This problem is plaguing me too. I can’t get past first base in creating my app. I am using Auth0 as the OAuth2 provider so my authentication URL is different to the OP’s but I see the exact same problem: the URL is prepended with https://zapier.com resulting in an invalid URL so fails on DNS.


  • Author
  • Beginner
  • 1 reply
  • Answer
  • August 7, 2020
avid.aml wrote:

+1 This problem is plaguing me too. I can’t get past first base in creating my app. I am using Auth0 as the OAuth2 provider so my authentication URL is different to the OP’s but I see the exact same problem: the URL is prepended with https://zapier.com resulting in an invalid URL so fails on DNS.


seems that this​​​​​​ is fixed now 

However you can do the flow manually, just remove the zapier.comhttps// part from the URL and start the flow from there, once you have a successful response just refresh the Platform UI(web console) page and on the testing bit you will see you are authenticated and just click on “Test Authentication” to validate that your /me endpoint works fine


  • New
  • 3 replies
  • August 9, 2020

Thank you, @ditorojuanf ! It is working for me now too.


I am having the same problem, can someone help me?


  • New
  • 3 replies
  • August 13, 2020

@renanoliveira I’m no longer seeing the same problem described in this post. However, testing the connection in the authentication configuration doesn’t work for me: I can see the OAuth workflow occurring but when calling my API endpoint, the JWT is missing or malformed. However, if I go to My Apps in Zapier and create a new connection then test it from there it works OK. Maybe you could try this.