Welcome Developers!

in

Welcome!

in

Are authenticated makeRequest working yet

Last post 02-15-2008 7:15 AM by OccuPal. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 02-05-2008 3:21 PM

    • Matt
    • Not Ranked
    • Joined on 02-05-2008
    • Posts 7

    Are authenticated makeRequest working yet

    I have the parameters set with:

    params[opensocial.ContentRequestParameters.AUTHORIZATION] = opensocial.ContentRequestParameters.AuthorizationType.SIGNED;

     But all I receive on my end is the owner and viewer ids. Is this part done yet?

    Filed under:
  • 02-05-2008 3:24 PM In reply to

    Re: Are authenticated makeRequest working yet

    Hey, it's not yet up and running.

      

  • 02-05-2008 5:32 PM In reply to

    • Paul
    • Top 75 Contributor
    • Joined on 02-01-2008
    • Posts 51

    Re: Are authenticated makeRequest working yet

    It is actually implemented on the proxy, but the correct parameter is not being passed in the request to the proxy.  So you can workaround this by supplying the parameter yourself in your url for now.  Simply include opensocial_authtype=SIGNED in your query string.  The SIGNED value is case sensitive.  With our next build the container will be adding the parameter itself so this is not needed.

     Additionally, you can use our OAuth tool to help you test your request handling of signed requests on your end.

  • 02-15-2008 6:22 AM In reply to

    Re: Are authenticated makeRequest working yet

     Any idea when this problem will be fixed?

     See Also: http://developer.myspace.com/Community/forums/p/326/1166.aspx#1166

  • 02-15-2008 7:15 AM In reply to

    Re: Are authenticated makeRequest working yet

    In summary, the problems with the makeRequest oAuth authentication appear to be:

    • Empty oauth_token parameter.
    • Empty oauth_signature parameter.
    • Invalid oauth_timestap
    Are there additional issues that we need to be aware of?
Page 1 of 1 (5 items)