On 09/20/2011 08:42 PM, Pete Zaitcev wrote:
On Mon, 19 Sep 2011 13:52:10 -0400
Matt Wagner<matt.wagner(a)redhat.com> wrote:
> I've spent a bit looking into this, and I think I have a decent
> understanding of the technical side of things. But what's not clear to
> me at all is the user story.
You are a step ahead of me, then. I am trying to understand what
is required from iwhd here. Care to help?
> 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).
> 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?
So far I managed to get by without installing what is tantamount to
an Amazon datacenter on my workstation, but it would be required hard
to do any development.
If you set up two legger oauth then iwhd would be an oauth server. It
would validate the requests using a shared secret in order to
authenticate the validity of the message.
I have not seen it stand alone, but have seen libraries for python,
java, and ruby.
-- bk