[WG-UMA] New issue #110: Consider adding optional location URI property to resource set description

Eve Maler eve at xmlgrrl.com
Fri Oct 31 10:19:20 CDT 2014


...possibly enabling us to kill issues #20 and #31 as well.

https://github.com/xmlgrrl/UMA-Specifications/issues/110

"With a property like this, the RS can inform the AS of not just the abstract properties of a resource set, but a specific property as well: its location, which can help the AS in term inform others that want to know. This could be useful not just for an UMA AS, but also for an OpenID Connect OP in the use case identified in the RSR spec introduction [http://docs.kantarainitiative.org/uma/draft-oauth-resource-reg.html#rfc.section.1], for feeding a distributed claims (or even aggregated claims) mechanism.

Nat and I discussed this while at IIW this week. It would be an extremely lightweight way to help solve an important portion of the personal discovery service challenge discussed in issue #20, as well as the resource "baskets" or "bundles" notion discussed in issue #31, because the application hosting the AS could also be an RS with a special "singular" UMA-protected resource set that consists of a set of pointers, OpenID Connect distributed claims-style (http://openid.net/specs/openid-connect-core-1_0.html#DistributedExample), to a variety of other OAuth-protected resource sets (possibly at multiple resource servers)."

Thoughts?

	Eve

Eve Maler                                  http://www.xmlgrrl.com/blog
+1 425 345 6756                         http://www.twitter.com/xmlgrrl



More information about the WG-UMA mailing list