Closed emadicio closed 2 years ago
Hi @emadicio,
From the release/tag 2.0.0 forwards of the SDK OAuth 1.0a support was removed, this new release only supports OAuth 2.0.
This is due to the fact that in the long term we do want to deprecate OAuth 1.0a in Bynder and only use OAuth 2.0. At the moment we don't have an official plan or timeline for the deprecation, which might still take a while.
In the meantime to still make use of OAuth 1.0a and permanent tokens, you will need to use one of the previous releases/tags.
Regarding permanent tokens for our OAuth 2.0 service we just finished implementing it. And at the moment we are adding this functionality to all our SDKs, what should be finished some time during next week.
Hi @danielsequeira,
Any update on the permanent token authentication with OAuth 2.0? We are moving to 2.0 at the moment and have not been able to make the authentication work.
Any help would be highly appreciated.
Regards, Leo
Hi @bitno , @emadicio ,
It should work using this method as indicated in readme :
const bynder = new Bynder({
baseURL: "https//portal.getbynder.com/api/",
permanentToken: "
@rcuisnier I've tried using the permanent token as described by the readme here but it's not working for me for calls like getAssetUsage
.
I think I found the potential bug here:
getAssetUsage
does not use this.api
and instead creates a new APICall
instance where the permanent token is not passed in.
Fixed in v2.3.9
Hey,
I was using OAuth1 and was working fine, but it seems like this library has been updated to OAuth2-only support. If I try to use my permanent OAuth2 token in the new way:
i receive an error message with code 401. Could you please provide guidance on how to authenticate with my permanent access token?
Thank you.