Sounds good. I submitted a PR to the wg-uma GitHub account [1] with the current policy manager draft. Also have attached a diagram to show the different extension that we’ve been discussing [2] (it’s the UMA Fedz spiral++) Best, - Alec [1] https://github.com/KantaraInitiative/wg-uma/pull/363 <https://github.com/KantaraInitiative/wg-uma/pull/363> [2]
On Sep 2, 2020, at 9:07 PM, Eve Maler <eve@xmlgrrl.com> wrote:
We continue the relationship manager work. Some things I think we need to figure out (ideally from proposals or lists of options):
- One API (AS only) or two (also RS)? - (Each) API protection model? - Topological and trust assumptions or lack thereof? What can be co-located? How many of each thing can there be? - Any rules needed for policy (“policy condition”) priority between RM and AS (the “cascading” scenario) - A clean way to model or illustrate the scenario when the RS is hosting claims (the “turtles” scenario) What else?
Eve Maler (sent from my iPad) | cell +1 425 345 6756 _______________________________________________ WG-UMA mailing list WG-UMA@kantarainitiative.org https://kantarainitiative.org/mailman/listinfo/wg-uma
