Hi all,
I picked up #2121 this morning, to integrate a warden authentication
strategy that provides two-legged OAuth. (Which someone described as
"our favorite catch-phrase ever.")
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.
I think we're actually trying to do two very different things with
OAuth.
One is to be an OAuth "server" that aeolus-image can connect to. I'm
thinking this is more a case of 3-legged OAuth, though, as I think we
want aeolus-image to have user-level permissions. (i.e., aeolus-image
authenticates the user to Conductor via token.)
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. (Actually, I'm thinking that we
want Katello to work both ways, and I'm not sure how this is normally
handled. I suspect that sometimes we'll want to make calls to Katello,
and other times they may wish to make calls to us.)
How many of these things are in scope for this sprint? How many of these
providers actually support OAuth on their end yet?
And how about #2309, "Ensure that owner information is stored as
meta-data in iwhd"? Does it make any sense to consider passing this
information along via OAuth from aeolus-image to Factory?
I'll tinker with getting some OAuth "stuff" in place, but it'd be
really
helpful if someone could help fill in the user story / use cases so that
it's not just an academic exercise on my part.
Best,
Matt