I have wanted to read private resources for a long time. And now I can do it (directly or indirectly via a third-party), using a combination of ticket wanted (per #87), ticket deposit, ticket grant, and a new grant flow that I call ac-obo (like #88). This also touches on #85, #84, and #83.
This is all not theoretical but real and has been implemented in my authorization server which does ac-obo and the applicable ticketing parts on its side, my reader (the third-party doing ac-obo) and an independent second-party (@fluffy-critter) serving some private resources and having the necessary ticket things on its side.
I have wanted to read private resources for a long time. And now I can do it (directly or indirectly via a third-party), using a combination of ticket wanted (per #87), ticket deposit, ticket grant, and a new grant flow that I call
ac-obo(like #88). This also touches on #85, #84, and #83.I have drafted a spec at https://github.com/omz13/indieauth-ticketing and rendered html into https://github.com/omz13/indieauth-ticketing-dist or just visit this. This also includes use cases to explain things, and drafts for the ticket things per issues here.
This is all not theoretical but real and has been implemented in my authorization server which does
ac-oboand the applicable ticketing parts on its side, my reader (the third-party doingac-obo) and an independent second-party (@fluffy-critter) serving some private resources and having the necessary ticket things on its side.