search

hitrust / google-wave-resources

Automatically exported from code.google.com/p/google-wave-resources
1 stars 0 forks source link

Feature Request: Implemented authenticated makeRequest for Gadgets API #366

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Requested in office hours.
Developers would like this feature.

Original issue reported on code.google.com by pamela.fox on 29 Oct 2009 at 4:21

GoogleCodeExporter commented 9 years ago

Original comment by pamela.fox on 29 Oct 2009 at 4:22

GoogleCodeExporter commented 9 years ago 
hi!  i'm @mort___ (on whose behalf this request was made in the latest office 
hours).  
the use case is to secure the communication between gadget and backend service 
in 
http://files.clackpoint.com/plugins/wave.xml - our audioconferencing gadget for 
wave.  
http://clackpoint.com/gadgets/wave/ (or mail me :) for info.

Original comment by richard....@gmail.com on 29 Oct 2009 at 4:26

GoogleCodeExporter commented 9 years ago 
How is this going to be different to the makeRequest api provided by OpenSocial?

see:
http://wiki.opensocial.org/index.php?title=Introduction_to_makeRequest

Original comment by Douglas....@gmail.com on 2 Nov 2009 at 2:10

GoogleCodeExporter commented 9 years ago 
it's not - it's the same api.  but as currently implemented, when called as 
gadgets.io.makeRequest() from a wave gadget, the only authorization method i 
can 
use is gadgets.io.AuthorizationType.NONE.  this means that parameters passed 
through the call cannot be authenticated.  contrast with, eg., our friend 
connect 
(opensocial) gadget, where gadgets.io.AuthorizationType.SIGNED is also 
available 
allowing parameters to be authenticated by the receiving server.

if there's already a way i can make the SIGNED authorization method available 
to the 
wave gadget, please let me know (along with the necessary keys to use the 
authentication when received)! 

thanks

Original comment by richard....@gmail.com on 2 Nov 2009 at 11:41