Hi,Eve
Having an RO literally being present to register a client operated by
some third party still seems like an unnecessary constraint to me if the
alternative is for RO to configure their preferences and then move on.
--I didn't catch the significance of it either. But I think Prabath's
Apologies for jumping in late.
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On
Behalf
Of zhou.suj...@zte.com.cn
Sent: Thursday, October 11, 2012 4:45 AM
To: Eve Maler
Cc: oauth@ietf.org WG
Subject: Re: [OAUTH-WG] Resource owner initiated OAuth delegation
Hi,Eve
If the client/requesting party is literally acting on behalf of the initial RO,
then it would seem to me that this is closer to the discussions of
redelegation and Twitter Echo and such from the past. UMA's use cases have to
do with authorizing delegated access that is performed on behalf of
