With the core specs basically out the door and seeing wider adoption and
publicity, the OAuth community is going to start to get more questions
about "how do I do X?", and many of these are questions that have been
answered before or seem "obvious" to those of us who have been up to our
ears in
The openID foundation is in a position of promoting OAuth 2 now as a
significant dependency of openID Connect and other work.
I can ask the board if there is a interest in hosting something specific for
OAuth 2.
I agree with Justin, now that the core spec is done there needs to be some
cons
Perhaps relatedly, in the UMA group we've been defining feature tests for
interoperability testing, and since UMA uses OAuth, we wondered if any OAuth
feature tests exist; we couldn't find any. That might be another activity
worthy of being taken up by such a community. (Both UMA and OpenID Conn
Not that I know of beyond what we have as part of the openID Connect testing.
A good number of those tests cover the underlying OAuth 2 flows.
It would not take too much to expand the FEDLAB test harness for more generic
OAuth tests if there was a demand.
Though without a protocol to apply OA
An interesting thought!
It is true that interoperability testing is a requirement for an
advancement of a Proposed Standard to Draft Standard, so surely OAuth
interoperability testing must take place. I I don't recall test suits
defined per se in the IETF. Not that it has not happened--it simp
+1 to StackOverflow -- that has become the goto source for programming FAQs
On Aug 23, 2012, at 7:38 AM, Justin Richer wrote:
> With the core specs basically out the door and seeing wider adoption and
> publicity, the OAuth community is going to start to get more questions about
> "how do I d
