Hi, Then, if the viewer allowed your information to be shared (as not anonymous), the restricted information as ViewerID will be sent to the third party server authenticated by OAuth?
Thanks On Jan 30, 10:56 pm, "Arne Roomann-Kurrik (Google)" <[EMAIL PROTECTED]> wrote: > ViewerID is a field that will not always be available to applications > (we don't want to share data about the viewer with the application > unless the viewer has explicitly allowed this information to be > shared). Orkut is expecting a push this Friday that will implement > access control lists, which should start giving users the option to > share their information with the application. Once this value is > shared, it can be sent back to a third party site. > > Hope this clears things up a bit, > ~Arne > > On Jan 30, 5:07 pm, JohnE <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Sounds good! =) > > > But, about the others essential data as viewerID? It will be > > authenticated by OAuth asopensocial_owneridcurrently? > > > Thanks > > > On Jan 30, 4:28 pm, "Arne Roomann-Kurrik (Google)" > > > <[EMAIL PROTECTED]> wrote: > > > Hi John, > > > > We know that the IDs currently don't match what you would get with a > > > Person.getId() call. I've filed a bug with the engineers to get this > > > issue resolved. > > > > Thanks, > > > ~Arne > > > > On Jan 29, 3:37 pm, JohnE <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > Yes, works fine now. But I think that lack on authentication some > > > > essential data for the development on third part servers (as viewer > > > > ID,opensocial_owneridas same of opensocial.Person.getId()). > > > > > Any idea about it? > > > > > Thanks > > > > > On Jan 29, 5:56 pm, pacheco <[EMAIL PROTECTED]> wrote: > > > > > > It works now: > > > > > > "Success! The data was validated" > > > > > > Tks Arne! > > > > > Pacheco > > > > > > On Jan 28, 10:08 pm, "Arne Roomann-Kurrik (Google)" > > > > > > <[EMAIL PROTECTED]> wrote: > > > > > > Hey, > > > > > > > Since that page was posted a change was checked into theOAuth > > > > > > library that breaks signing requests. For more information, a bug > > > > > > has > > > > > > been filed here: > > > > > > >http://code.google.com/p/oauth/issues/detail?id=7 > > > > > > > Until the patch is committed to the project, you can try this > > > > > > fix: > > > > > > > Change the line inOAuth.php that reads: > > > > > > if( $parts['port'] != '80' ){ > > > > > > to > > > > > > if( isset($parts['port']) && $parts['port'] != '80' ){ > > > > > > > Please let me know if that resolves the problem. > > > > > > > Thanks, > > > > > > ~Arne > > > > > > > On Jan 28, 10:28 am, pacheco <[EMAIL PROTECTED]> wrote: > > > > > > > > Lane / Arne, not working for me either: > > > > > > > > "This request was spoofed" > > > > > > > > Anyways, tks for the explanation... > > > > > > > > Did anyone found a way to implement it successfully? > > > > > > > > Thanks in advance > > > > > > > Pacheco > > > > > > > > On Jan 24, 11:12 pm, Lane LiaBraaten <[EMAIL PROTECTED]> wrote: > > > > > > > > > Hi Everyone, > > > > > > > > > Arne put together a page with information on how to use the > > > > > > > > makeRequest method to send signed requests to your server. His > > > > > > > > examples include both client-side gadget code and some PHP code > > > > > > > > that > > > > > > > > runs on the server to validate the request. > > > > > > > > > Check it out > > > > > > > > here:http://groups.google.com/group/opensocial/web/validating-signed-reque... > > > > > > > > > Cheers, > > > > > > > > Lane --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Orkut Discussion" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-orkut?hl=en -~----------~----~----~----~------~----~------~--~---
