I'm using the myob.accountight.sdk in my app to connect and extract data from the MYOB database, however this evening I'm encountering the error:-
"Encountered a validation error
(https://secure.myob.com/oauth2/v1/authorize)"
Is MYOB encountering issues or has something changed (this afternoon) on the server side to cause the app to error?
thanks
https://community.myob.com/discussions/accountrightapiquestions/c-webbrowser---webview2-solution/877141
We are still having issues with this. Any suggestions?
We've had multiple users report this same problem overnight and today. Definitely not fixed from the MYOB side.
Hi Folks
I have isolated the problem myself and have created a 100% workaround - however, I don't use the MYOB SDK - I wrote my own access code from the ground up using VBA Access as all my clients use MS Access databases.
The problem is as follows - and I have managed to generate all the errors to confirm.
In a nutshell - it is the MYOB token server handing out refresh initiated access_tokens.
To explain - you got to force the server to give you a new 7d Refresh code which comes also with a 20 min access_token - this works 100% and gives me 20 minutes of access.
To regain access I flush the expiry date to be less than today and at the refresh corner - tell it no get a new code.
If you refresh the MYOB Server gives you a token for an offline file and the token is something like "org_........ " when it should be "AAE.... at the end of the token you will see the scope - it is wrong.
Anyway - I fell across this problem because my trial app I built years ago to test all this didn't have an auto-refresh - it just got a new 7d code.
All my clients are up and running but I have had to jury rig the access token code.
But it works 100% - the problem is MYOB's refresh issue server!
Sorry I can't help with the SDK - I am a C# & a VB.Net person but other than getting the VB SDK working 3 years ago I never used their code.
Regards The Doc
After making further changes in our app to handle what may be a change in the response content, our app is now working correctly. All of our clients will probably need the upgrade.
We're seeing a lot of issues relating to this as well - started around 6:30pm on 7th August but escalated today as customers on our apps are processing payroll. Started off returning a large number of "invalid_grant" errors, and as customers have re-authenticated we've started seeing "The supplied OAuth token (Bearer) is not valid" instead.
We're investigating app code changes to try and mitigate this/determine any latent issues in our authentication. @tanvir are there any further updates on why this has started happening recently/what changes are occurring in the identity services?
HI @tanvir, the issue has seemed to be resolved now, although some recent posts suggest otherwise. No code changes were required either, BUT did you find out the root cause of the issue.
Two things that concern me however; (i) the randomness and unpredictability of these issues that did have a critical impact on our production processes, and (ii) the slow acknowledgement that there was a problem and that MYOB were working on it. At least an acknowledgement would have avoided second guessing of what could be causing the failur to connect to the MYOB Cloud file.
Hi all, our apps have also been affected by this issue, and for some reason I have not been receiving these posts, even though I thought I had previously applied the forum tick box.
After making changes in our app around the authorisation code, we receive an "invalid grant" error, which has been overcome by basically re-authorising. However, this solution is not working for everyone. We will try the suggested fix above and advise further.
This worked for me but I had to force the app to GetTokens. If your code looks like below, comment out the null test temporarily so GetTokens is executed:
//Get tokens if not stored
if (_oAuthKeyService.OAuthResponse == null){ var oauthService = new OAuthService(_configurationCloud); _oAuthKeyService.OAuthResponse = oauthService.GetTokens(OAuthLogin.GetAuthorizationCode(_configurationCloud)); }
Hi, If the above solution is not working for you, please raise a support ticket here for further investigation - https://apisupport.myob.com/hc/en-us/requests/new?ticket_form_id=215283
This did not work for me
Hi All, Apologies for the inconvenience. Please try to revoke access and then reauthenticate. Please see below articles;
We have developers confirming that getting the MYOB user to revoke access and then reauthorizing the API key; resolves the issue. At this stage we are not sure what actually caused this issue, but identity services are going through some changes which may have caused this issue. We will find out.
How do we elevate this so it gets attention?
I have the same problem too. Started 7 Aug around 10pm.
I've been having the same problem since yesterday also.
The work-around is to delete the Token information, that is stored in IsolatedStorage (C:\Users\[user]\AppData\Local\IsolatedStorage. This forces the app to go through the auth process and app works. However, it appears that when the Token expires the issue presents again.
I've made no code changes and appears that some change has been made in the MYOB back-end to effect the behavior of my app. Does MYOB, or anyone else have a resolution to an issue that appeared yesterday and remains unsolved atm?
Our clients are experiencing the same issue using our App since yesterday
All my clients are getting this error since yesterday. Are there API changes?
We are getting the same error with one of our clients. Unable to get any data from MYOB. We are using the myob.accountight.sdk as well.
Self-help & Learning
Level up your skills and find answers across all MYOB products
Help Guides
MYOB Academy
