[Openid-specs-heart] An approach to data portability for the RO's policies

[Eve Maler]

In a conversation today with Debbie, Ken, and Nancy, an old idea came to
mind that I thought I'd capture in a diagram. Here's a short slide deck
<https://www.dropbox.com/s/pjrno6mm9jencwv/Data%20portability%20for%20UMA.pdf?dl=0>
illustrating the idea: The AS would present an UMA-protected API enabling
Alice to share her policies out of the AS where she configured them in the
first place to other places (say, other AS's that she wants to use instead,
or for backup or federated policy management purposes).

----

(Keep in mind that an AS isn't actually required to store policies at all;
they don't appear on the UMA wire. However, this service is the common
facade where tokens do get issued after authorization assessment, and it's
natural to build an AS on top of existing access management components that
actually do policy handling and evaluation.)

----

(Of course, a policy API could also allow *writing* policies in to this
location from other authoritative sources. :-) )


*Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
*ForgeRock Summits and UnSummits* are coming to
<http://summits.forgerock.com/> *London and Paris!*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20160830/379434ae/attachment.html>