I give up: How do you get the OAuth 2.0 temp token for e.g. PostMan work?

Steve Klett Strategic Partner

• December 10, 2022 02:34

WARNING - this isn't really an Integrator.io ("IIO") question, but I'm thinking IIO devs will have experience with what I'm struggling with.

I've somehow been lucky in my ability to avoid setting up OAuth 2.0 connections or clients, that luck ended today  :(

 

I've setup an IIO HTTP connection using OAuth 2.0 to LightSpeed (retail POS system). I succeeded with the IIO connection. Now I want to do dev work in PostMan but I need the temporary token that is supplied in the authorization callback. The problem is, I never see that; IIO handles all of it for me.

I've tried debugging the connection and re-authorizing to see if I could intercept the temporary token and quickly use it in PostMan before it's 30 second expiration. No luck, the debugger didn't capture anything.

I think my question can be succinctly stated as: How do you use PostMan with OAuth 2.0 when your client registration with the API has a IIO callback URI?

Now that I think about it, maybe another way to skin this cat is to skip the temp token and use the Access Token that IIO knows about? Assuming that makes sense, can Celigo provide that Access Token to me? Is there a way to see it?

I apologize if I've bungled the OAuth terminology, as I said at the top I'm brand new to this stuff.

0

• 

  David Gollom Strategic Partner

  • December 10, 2022 23:22

  

  

  

  

  

  Hey Steve,

  It's all in the callback URL. In IIO the callback is going to go to IIO with the initial token. 

  I have another app setup in Lightspeed that we can use with Postman.  It's setup with a callback url that feeds the initial access token back to PostMan so that. 

  I can show you how to set it up.  I went through all this pain with a Hubspot project a while back.   

   

  0

Please sign in to leave a comment.