Hello, On Fri, Nov 29, 2013 at 9:23 PM, Kanavin, Alexander < [email protected]> wrote:
> Hello Jaehwa, > > I just want to clarify one more thing because it's not mentioned anywhere. > For authenticating with service providers that support OAuth 1/2, it's most > sensible to use the existing gSSO OAuth plugin, because it can handle a > long list of service providers, including major ones such as Google, > Facebook, Yahoo, Microsoft, etc. You can avoid writing custom > authentication code for each of these: > http://en.wikipedia.org/wiki/OAuth#List_of_OAuth_service_providers > > The OAuth plugin requires a gSSO UI component for displaying user > authorization webpages. We have a reference UI written using Gtk, but for > Tizen there needs to be a Tizen-specific UI. Is that your plan, or do you > have some other approach in mind? > Yes. we will provide a Tizen-specific UI component. I mentioned this on the attached issue note but not in the email because I thought we should provide a UI component and there will be no argument with it. As you mentioned, oath is widely used by many well-known services. Recently, we've released Tizen Twitter SDK. We wrote our own code for auth1 including UI for user interactions for the SDK and felt it wasn't simple work. I'm sure it would be much easier to develop Twitter SDK if we had gSSO & UI. So I think providing UI component is one of the mandatory features of Tizen SSO. Regards, Jaehwa
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
