Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I athenticate by client credentials flow in Sandbox env? #171

Open
jossperdomo opened this issue Apr 14, 2019 · 4 comments
Open

Comments

@jossperdomo
Copy link

jossperdomo commented Apr 14, 2019

Recently I tried to authenticate using my sandbox business user by client credentials flow. I did the following request

curl -X POST https://api-sandbox.uphold.com/oauth2/token \
>   -H "Content-Type: application/x-www-form-urlencoded" \
>   -u <client-id>:<client-secret> \
>   -d 'grant_type=client_credentials'

But I receive as response

{"error":"unauthorized_client"}

Could anyone please help me with this? Thanks!

@tycooperaow
Copy link

Yeah, I'm receiving the same error,

@eiromz
Copy link

eiromz commented Jun 10, 2020

did anyone resolve this

@osmtechnologies
Copy link

osmtechnologies commented Aug 12, 2020

yeah, I'm facing the same error,

I think its come when account not verified

@waldyrious
Copy link
Contributor

Apologies for the late response, folks. It's likely that the issue you were facing was due to the requirement that only manually approved accounts can request an access token using the client credentials flow. This is indicated in the documentation as such:

For business usage only you may choose to use client credentials authentication. This requires manual approval from Uphold.

...but it wasn't made explicit that this also applied to the Sandbox environment.

The good news is that we recently removed that requirement for the Sandbox environment (it's still in place for the production environment), so you should now be able to use the client credentials flow to obtain an access token. We'd appreciate if you could confirm that the issue is solved, so that we can close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants