Awesome-Mirrors/decentralized-id.github.io
1
0
Fork 0
mirror of https://github.com/Decentralized-ID/decentralized-id.github.io.git synced 2024-10-01 01:05:54 -04:00
Code Issues Packages Projects Releases Wiki Activity
d88e61056a
decentralized-id.github.io/_posts/identosphere-dump/open-standards/authorization/README.md
⧉ infominer 28856e3c8c auth, complementary, exchange
2022-12-03 00:15:04 -05:00

6.3 KiB
Raw Blame History

Authorization Protocols

oCap

  • Hygiene for a computing pandemic: separation of VCs and ocaps/zcaps
    • You could implement zcap-ld on top of VCs…
    • However, you're actually squishing together what should be a separation of concerns in a way that will become unhygienic. Like a lack of proper biological hygiene, the result is sickness in our computing systems.
    • The observation of "these things seem so similar though!" is true, but you can already make that claim even if you're just looking at the linked data proofs layer. VCs and zcap-ld diverge from there for two very separate purposes: what is said, and what is done.

This week’s CCG teleconference had a great discussion about object capabilities

Alan Karp:  I've been doing capabilities since I reinvented them in 1996 and I want to make sure we get it right, because when newbies start to use them there are plenty of mistakes that can be made

[...] A capability or an OCAP is an unforgeable, transferable, permission to use the thing it designates ... it combines designation with authorization

I was reading zcaps draft, as well as related work, mostly macaroons (https://research.google/pubs/pub41892/.

Something that I found confusing  about capability documents is that they do not make clear the actions they concern. For example from this https://w3c-ccg.github.io/zcap-ld/#example-1 it is not clear that this is a capability for "driving a car".

We are still trying to figure out how to explain these things to people.

Capabilities-based systems are not a new concept; they're decades old at this

point. The challenge has always been in communicating why they're useful and

have a place in modern security systems.

The Encrypted Data Vault work uses zcaps, and it's there that we're trying

hard to explain to developers how to use it:

After ruminating on ZCAPs, VCs, DIDs, and DID Documents over Easter dinner, it occurred to me that we're on the verge of creating a model for a "verifiable" economy...

https://www.notion.soimages/image3.png

I see all of this converging into a Capability Authorization-enabled Decentralized Object Model.  “More news at 11…”

https://www.notion.soimages/image1.png

Updates on Kepler including implementing support for CACAO-ZCAPs, improved the put function to make it easier to store objects of different types, and added support for listing objects by prefix: kepler-sdk#40 kepler#115.

  • The ezcap library - Manu Sporny

    Now might be a good time to announce some open source tooling a few of us have been working on related to zcaps that is being created to simplify the developer experience when developing with zcaps.

  • ezcap (pronounced "Easy Cap") - An easy to use, opinionated Authorization Capabilities (zcap) client library for the browser and Node.js.

UCAN

these are the types of use cases that we think can be created and enabled across the web as an open, interoperable standard. And some of it crosses into the work we're doing as part of the Decentralized Identity Foundation, too.

  • User Controlled Authorization Network model and how it contrasts with decentralized approaches
  • APAC/ASEAN Community Call now a colloaborative initative between DIF and ToIP, launched Thursday 26th May 2022, kicking off with an IIW34 recap. (Recording A couple weeks ago Amber Case came and spoke about “Calm Technology” at the TOIP Human Experience Working Group (HXWG