On Tue, Sep 20, 2011 at 06:42:32PM -0600, Pete Zaitcev wrote:
> The other is to act as an OAuth client when connecting to other
> services, using two-legged OAuth. Off the top of my head, we want to be
> consumers of Katello, iwhd, and Factory.
In the terms put forward by the RFC-5849, is iwhd a "client" or
"server"?
I presume it cannot be "Jane" (or her user-agent).
I think Bryan already answered this, but I'd think of iwhd as the server
here, as it's responding to authenticated inbound requests.
> One is to be an OAuth "server" that aeolus-image can
connect to.
Does this thing -- an OAuth server -- exist as a free-standing component?
Not really. It's an authentication scheme that each app should ideally
support. (I answered 'Not really' instead of 'No' because it occurs to
me that you could implement this as a proxy server that only passed
authenticated requests along, but it would still have to sit in front of
each app, not as a central shared service, so I'm not sure it really
makes any sense here.)
-- Matt