This is not officially documented, but I'd recommend sticking with Google's convention of using "anonymous" as the consumer key, and "anonymous" as the consumer secret.
See bullet point #2: http://code.google.com/apis/accounts/docs/OAuth_ref.html#SigningOAuth Allen On 2/25/10 7:43 AM, "Jeff" <[email protected]> wrote: > Hi, > > I need a bit of clarification. A project I am working on will allow for > anonymous consumers. I know some implementations do this by having an > open consumer key and secret. I cannot find any place in the spec if > this is specified. E.g. setting both to "public". So is this just left > up to implementations? > > Thanks! > > -- jj -- 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.
