search

yadayada / acd_cli

An unmaintained command line interface and FUSE filesystem for Amazon (Cloud) Drive
Other
1.35k stars 167 forks source link

Documentation not correct for "Advanced Users (Security Profile)" #392

Open jerblack opened 8 years ago

jerblack commented 8 years ago

Since the primary (simple) authentication method stopped working, I was trying to make the "Advanced Users (Security Profile)" steps work but the steps talk about creating a security profile, and in the process select options related to the scope and redirect URL, but at no point while creating the security profile are those options presented. It looks like Amazon updated their developer portal since making the Drive API invite only, and now we no longer see the same options.

Can we do this?

  1. Figure out how to make this process work.
  2. Document it step-by-step here: http://acd-cli.readthedocs.io/en/latest/authorization.html
zmwangx commented 8 years ago

It's been a long time since I created my security profile (and IIRC it was indeed quite confusing), but I just tried to create another one, and here are some screenshots. It should answer your question about the redirect URL. As for whitelisting and scope, I don't remember and can't find how to do that, so good luck. Maybe try without that first.

screen shot 2016-09-01 at 9 33 34 am screen shot 2016-09-01 at 9 34 04 am screen shot 2016-09-01 at 9 34 22 am screen shot 2016-09-01 at 9 35 16 am screen shot 2016-09-01 at 9 35 26 am

P.S. I know the app ID is exposed in the screenshots. But don't try to hack me, I'll delete that demo profile anyway 😜

zmwangx commented 8 years ago

Turns out the reason I can't figure out how to whitelist the profile is that whitelisting is now invitation-only (thanks @isleshocky77 for pointing out).

Indeed, https://developer.amazon.com/public/apis/experience/cloud-drive/content/getting-started now reads

You must be invited into the Amazon Drive API service to whitelist your app for Amazon Drive or you will not be able to send any node-related requests.

and in March it read (Wayback Machine)

You must whitelist your app for the Amazon Cloud Drive or you are be able to send any node-related requests. You must whitelist your Security Profile by completing the whitelist request form.

isleshocky77 commented 8 years ago

@zmwangx No problem, was just about to document the reason in this issue as well. I would say you can probably close this issue and one of the other ones. I was hoping it might be a quick process, but the fact that they had me send an email and not fill out a web form to be invited gives me little hope.

zmwangx commented 8 years ago

I would say you can probably close this issue and one of the other ones.

Well I'm not a collaborator on this repo, just a regular dude trying to help out (to little avail) 😉

isleshocky77 commented 8 years ago

Change took effect August 2, 2016 per Official Release https://forums.developer.amazon.com/articles/33185/the-new-amazon-drive-api-and-sdks-for-android-and.html

jerblack commented 8 years ago

So is that the end of ACD_CLI then?

zmwangx commented 8 years ago

So is that the end of ACD_CLI then?

No, my old profile is working just fine. So should @yadayada's public one. I guess someone just abused the service and the outage is temporary.

zmwangx commented 8 years ago

Change took effect August 2, 2016 per Official Release https://forums.developer.amazon.com/articles/33185/the-new-amazon-drive-api-and-sdks-for-android-and.html

Oh wait, "the new Amazon Drive API"... Does that mean we're on a legacy API that is being phased out? At a glance I don't see any difference in the API documentation though: https://developer.amazon.com/public/apis/experience/cloud-drive/content/nodes. (I mean, compare it to, say, last year's version.)

dellipse commented 8 years ago

"The new Amazon Drive API and SDKs for Android and iOS are available by invitation only, starting August 2nd, 2016"

I didn't think we were using those APIs. We are not running on those platforms.

On Wed, Aug 31, 2016, 11:46 PM Zhiming Wang notifications@github.com wrote:

Change took effect August 2, 2016 per Official Release https://forums.developer.amazon.com/articles/33185/the-new-amazon-drive-api-and-sdks-for-android-and.html

Oh wait, "the new Amazon Drive API"... Does that mean we're on a legacy API that is being phased out? At a glance I don't see any difference in the API documentation though: https://developer.amazon.com/public/apis/experience/cloud-drive/content/nodes .

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/yadayada/acd_cli/issues/392#issuecomment-243968432, or mute the thread https://github.com/notifications/unsubscribe-auth/AHXrWIDUFOn8q_6E4NAfvzCkKbZqezWuks5qlkqygaJpZM4JyN1y .

zmwangx commented 8 years ago

I didn't think we were using those APIs. We are not running on those platforms.

We are using the REST API.

isleshocky77 commented 8 years ago

@dellipse This was in relation to setting up your own Security Profile. You can't whitelist the app without having the Cloud API enabled. You can no longer have that API enabled without being invited.

m4vr0x commented 7 years ago

So if i understand well, new acd_cli users can only use Simple (Appspot) authorization method ? :-(

awilliamson commented 7 years ago

@m4vr0x Yet the 'Simple' ( Appspot ) method doesn't work due to #416. This leaves us in a bit of dilemma here. Newly created security profiles cannot be whitelisted, and the old auth method is rate limited to the point of uselessness. @yadayada Any suggestions?