[#8200] Aviary's Phoenix image editor support
Summary Aviary's Phoenix image editor support
Queue Ansel
Queue Version Git master
Type Enhancement
State Accepted
Priority 1. Low
Owners
Requester Michael Rubinsky <mrubinsk (at) horde (dot) org>
Created 04/20/09 (325 days ago)
Due
Updated 08/01/09 (222 days ago)
Assigned
Resolved
Attachments
Milestone
Patch No

History
08/01/09 Jan Schneider Version ⇒ Git master
 
05/04/09 Michael Rubinsky Comment #3 Reply to this comment
Signed requests will be a part of the forthcoming Advanced API:



http://aviary.com/thread?tid=1547&p=2#46187
04/23/09 Michael Rubinsky Comment #2 Reply to this comment
Looking at this further, I think we should probably wait until this 
API matures a bit, or the "advanced api" version is implemented. With 
the simple API there is no shared secret between the client server and 
Aviary, only a client specified identifier for each image that is 
passed to Aviary in a GET request.  After saving the image, Aviary 
POSTS back to the client server a URL to find the new image, along 
with the same identifier that was originally passed in the clear via 
GET. So, unless I'm missing something, it would theoretically be 
possible for a 3rd party to hijack this identifier and cause the 
user's image to be replaced.
04/20/09 Michael Rubinsky Comment #1
State ⇒ Accepted
Patch ⇒
Milestone ⇒
Queue ⇒ Ansel
Summary ⇒ Aviary's Phoenix image editor support
Type ⇒ Enhancement
Priority ⇒ 1. Low		 Reply to this comment
Implement Aviary's API for image editing as an optional editor in 
Ansel. Thanks for the find, Chuck!



http://aviary.com/apidocs