Postman updated - old oAuth callback URL has been deprecated

Question

The existing postman collection for MYOB contains a redirect_URI which has now been deprecated.

This postman discussion discusses the issue and proposes an alternative URI for {desktop | web } use.

This prevents the...

"Check if there is a typo in fhbjgbiflinjbdggehcddcbncdddomop.chromiumapp.org"

error from occurring when testing authentication.

However I'm still getting

"We have encountered some issue with the request, please try again later or contact your app support

invalid_request"

and am wondering how to get around this issue. I had this working around 3 weeks ago; now nothing is working :-(

Could you recreate the video on how to get started on oAuth/authentication in MYOB with this new info?

thanks,

Dale

hannah_b · Answer

HI&nbsp;SirDale,
&nbsp;
Thank you for reaching out.&nbsp;Yes that is correct, The Postman redirect URI of&nbsp;https://www.getpoastman.com/oauth2/callback&nbsp;has recently been deprecated. What you will need to do is update the redirect URI to the new value ofhttps://oauth.pstmn.io/v1/callback. This will need to be updated In My.Myob and your app when completing OAuth.&nbsp;
&nbsp;
Let us know if you have any questions,&nbsp;
&nbsp;
Thanks,&nbsp;

sirdale · Answer

Hi,&nbsp;I made the change to postman (redirect_uri set to&nbsp;https://oauth.pstmn.io/v1/callback) but all that happens is that postman then gets a web page from MYOB with...&nbsp;"Sign in to MYOB" (username, password fields shown), as well as&nbsp;&nbsp;"Uh-oh! The numbers don't add up." saying javascript isn't enabled, as well complaining about no cookies.&nbsp;But this is to be expected given postman is not a browser.If I change the redirect_uri to be "https://oauth.pstmn.io/v1/browser-callback" then I get the same response.If I grab the initial web request from postman's consolse...&nbsp;https://secure.myob.com/oauth2/account/authorize?client_id=&lt;my client id&gt;&amp;redirect_uri=https://oauth.pstmn.io/v1/browser-callback&amp;response_type=code&amp;scope=CompanyFile&nbsp;and put that into a browser (as demonstrated in the video) I don't get the MYOB authorisation page, but instead just get...Authentication completeYou can close the tab and go back to the Postman app.&nbsp;I had this running previously, but am completely stuck at the moment. I'm unable to make any progress until I can get authenticated.&nbsp;Please help!

Forum Discussion

Postman updated - old oAuth callback URL has been deprecated

Related content

Postman Collection Page gives a 403 error

sharing postman myob files to sharing postman myob files to collaborate

How to access data using Postman from Advanced API

Cannot access local file via postman.

Bug in OAuth2 callback: 'state' parameter not set when redirecting after user declines to authorize application.

“IMPORTANT NOTICE”: TLS versions 1.0 and 1.1 Deprecation 20 November 2021

Error when authorize the application

Re: Redirect Uri when Registering App