Iâve browsed through this forum and ruled out these possible reasons for the error:
redirect_uri is the same for first âauthorizeâ request (which works; I get back the temporary code) and the actual âaccess tokenâ request (which fails with above error)
I send it as âapplication/x-www-form-urlencodedâ
âif_tmp_codeâ â is the âcodeâ URL parameter value grabbed from the URL after redirected back to my app (after Infusion completed step âRequest Permissionâ).
âredirect_uriâ â is the same URL we just where redirected to from Infusion (after Infusion completed step âRequest Permissionâ) - without the url parameters (e.g. âcodeâ or âscopeâ).
â
What do you think about this?:
I would double check that the redirect_uri matches what you registered with in the developer portal
Is this advice outdated?
If no: Could you point me where I need to âregisterâ the redirect url in the dev administration app?
(two years old) is heavily used (accessed via Infusion-PHP-SDK).
(two years old) is occasionally used (accessed via Infusion-PHP-SDK).
(new one, which I plan to use to replace the two above ones; use NodeJS) is in âwaitingâ state for two weeks now (see here).
Long story short, I couldnât afford to delay development of my newest api wrapper until the third app is approved by Infusion, so I decided to access, for the time being, the second app.
Question: May this be the reason of my troubles? Is it ok to request an access_token with âInfusion-External-App-Bâ if there is already an access_token for âInfusion-External-App-Aâ for one âInfusion-Internal-App-Registrationâ?
If youâre reusing an existing Application key, youâll need to proxy the callback through that to your new app, but you would then be reusing quota from the first one.
This error will result from an app in mashery that has not yet been set active but is still in a pending status. Check mashery to be sure but thatâs one of the most common reasons for the message.
Sorry for the delay in getting back to you. This is caused by your client_id not being active. So either either the client_id has been deleted or is in a waiting state. Hope this helps. Also I would check to make sure you are using the right client_id.
Hi there? I face the same problem, I keep getting invalid_client, everything seem correct, yet still getting the error invalid_client. When I check on my return header I got this:
You will need to provide what your request looks like url, payload, header, etc so we can help. Mask you client_secret and any authorization code though, because that is sensitive data.