Hi, Manish > Why would an SP need the details of a consumer, other than the about/ > registration information and what it is trying to do with the customer > data (to be shown on the authorization page)? Can you elaborate with a > use case?
I think about following Usecase. - SP: Examplesp.com - Consumer: Exampleconsumer.com 1. User exports the resources of Examplesp.com to Exampleconsumer.com in OAuth flow. 2. Exampleconsumer.com combines the resource that imported with own service and makes a more attractive resources. 3. Exampleconsumer.com exports in Examplesp.com with much number of the users to promote the use of the resources. After Step3, roles of both are replaced. Exampleconsumer.com implements a logic of "OAuth SP" and will issue Consumer Key to Examplesp.com. However, both share ConsumerKey(+Secret) which Examplesp.com issued. In addition, they may share the User Identifier(OpenID url or xoauth_yahoo_guid or gmail etc...). I think that data access between cooperating SP,Consumer is activated by defining expansion specifications using these. Do you ignore this use case as a special case? Regards, Ryo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" 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/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
