I've got a system (Elgg) that both acts as an OAuth Service Provder
and provides library hooks for plugins wanting to be OAuth consumers
of other things. Consumers and tokens and all the mechanics work
great, but what I'm struggling with is what to *call* things so that I
and the end-user can tell them apart. Basically, we've got four
different things to keep track of:
Service Provider
Consumer: external consumer of my local site
Token: saved request and access tokens for my local users
accessing the API via OAuth from another site
Consumer Library:
Consumer: locally-based consumer of an external service provider
Token: locally-stored request and access tokens for accessing
external service providers
Right now I've just got a big table of consumers and tokens, and it's
starting to get out of hand. I'm just going in circles with how to
best denote what's what and how to present all of this to the end
users.
Any thoughts from the community? Has someone else implemented both
sides of OAuth in one site before, and if so what phrasing did you use
for things?
-- Justin
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
