Closed EmilTemirov closed 9 years ago
Thanks for the report and sorry about the problems you're seeing. In reverse order...
Have you tried a url of so:
/oauth/authorize?client_id=_&redirect_uri=_&response_type=code&scope=public+edit_assets
This isn't documented well i'm noticing and we'll work on that but it should work OK.
Thanks! I tried to obtain access_token using authenticated code. I sent requests to https://api-sandbox.gresb.com/oauth/token with Form Data params:
But I always got the _invalidrequest error:
{
"error": "invalid_request",
"error_description": "The request is missing a required parameter, includes an unsupported parameter value, or is otherwise malformed."
}
What was I doing incorrectly?
And I found a bug in the sandbox: authenticated users have access and permissions to view and editing not their own Applications.
The missing parameter is grant_type=authorization_token . This was missing from documentation, but has now been added.
So your request should look like:
curl -X POST 'http://gresb-reports.dev/oauth/token?client_id=...&grant_type=authorization_code&redirect_uri=...&client_secret=...&code=...'
grant_type=authorization_token - it's not work for me, but grant_type=authorization_code - work fine
You're right of course. Sorry about that typo. I'll close this but reopen and let me know if have other issues.
I have some problems with OAuth authorization in https://api-sandbox.gresb.com