I need to be able to securely identify the user on the back end,
preferably with their email address. Does anyone have any example of
this? I know it seems pretty basic, but I'm just getting started.
--~--~-~--~~~---~--~~
You received this message because you are
Hey Kenny,
From your email I'm not entirely sure what type of application you're
building, so that makes it somewhat harder to comment on what the right
approach would be, but in a general sense my comment would be that you're
thinking the wrong way around for a social app.
In the clasic a user
You can should us signed requests, then you'll get the oensocial_user_id,
and validate the request signature using OAuth.
On Wed, Sep 9, 2009 at 9:37 AM, Kenny Dunn gkennyd...@gmail.com wrote:
I need to be able to securely identify the user on the back end,
preferably with their email
Your time frame for when you want to release will drive your choice of
platform. If it's immediate you will need to either write for 0.8
containers or write an external app on top of the OpenSocial REST
endpoints and make use of one of the SDKs out there. If your time
frame is in the 4-6 month
