You only need one consumer key/secret if you have one consumer application. For web applications, I usually put my consumer credentials in a local config file.
Leah On Thu, Dec 3, 2009 at 11:04 AM, rob ganly <[email protected]> wrote: > hi guys, > > so i'm implementing oauth 1.0a (consumer and service) and have a hard- > coded consumer_key and consumer_secret on the consumer side (in a > config file). i was envisioning having one pair for each consumer > (i.e. individual site/ application) that is to use the service as i've > seen before. > > however i've also seen it suggested/implemented that each individual > user (even coming from the same consumer) use their own unique > consumer key, despite having their own unique user credentials. > > in the consumer table i have, that i adapted from an example, each > consumer has one user id associated with it, whereas i would've > imagined the relationship between consumer and user to be one to many. > > any ideas/pointers/clarification gratefully received! > > best, > > rob ganly > > -- > > 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] <oauth%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/oauth?hl=en. > > > -- 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.
