There's also this means of providing identifying instance information for a
single client registration:
http://tools.ietf.org/html/draft-richer-oauth-instance-00
This is solving a different need and can be used in tandem with, or in lieu of,
the dynamic registration per-client, depending on you
It's officially still "up in the air", as the WG and its chairs are trying to
figure out whether the MAC draft is worth resurrecting as-is or if there's
another, more general solution to signing-based tokens that can work.
Current thinking, after a session at an IIW earlier today on this very to
Hi Igor-- If you mean enabling (um) Grandma Goldie to delegate child pickup
duties to Tom the Taxi Driver after having been herself delegated to pick up
the child by Peter Parent, then -- as long as we're focusing on policy-based
claims-tested authorization for requesting party access, then UMA
Sorry for the delay. Here's what I was thinking about:
https://dev.twitter.com/docs/auth/oauth/oauth-echo -- The delegation here
(using OAuth V1) is about client 1 delegating to client 2, still presumably
operated by the same human user throughout.
http://tools.ietf.org/html/draft-vrancken-oauth
What is the future of
http://tools.ietf.org/html/draft-ietf-oauth-v2-http-mac-01, which already
expired? Is it going forward?
Thanks
Pedro
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
