-
Similar to encryption, we should also add a section on our supported JWS algorithm. We should also ensure that this is aligned with https://github.com/w3c-ccg/lds-jws2020
awoie updated
4 years ago
-
RP should communicate with Issuer through Router, rather than calling directly and vice versa.
The Hub Router should have the ability to create a connection with third party (user facilitates the c…
-
The `did:peer` VDR is producing docs with incorrect IDs for `authentication`:
Example
```json
{
"@context": [
"https://w3id.org/did/v1"
],
"authentication": [
…
-
Initial Release for the RP Adapter and the Issuer Adapter.
## RP Adapter
The Relying Party (RP) Adapter enables standard OpenID Connect flows on top of DIDComm. It exposes a standard OpenID Conn…
-
Extending #352 and #385, make pack/unpack invoke an injectable crypto-operator (could call it a crypter and do some renaming) for all encryption, decryption, AEAD, etc, using format-agnostic parameter…
-
I noticed the examples in the didexchange RFC are inlining the signing keys in the `request` and `response` messages as `did:key`s as per the attachments RFC, eg.:
```jsonc
{
"@id": "5678876542…
-
- [x] access control for dashboard page (only logged in user should access dashboard). Other pages like DID management, relationships and dev mode pages can still be accessed without login. https://gi…
-
In the composite package, there's an encryption type called "DIDCommEncType", but the JWE encryption code should not have any DIDComm-specific stuff in there. It becomes a problem for other projects w…
-
At time of writing, DIDComm has this PDF linked from their homepage but not from the JS repo at dif:
https://drive.google.com/file/d/1gkzkEUw1oa8vECorlLBSRCp2vgT7aqmh/view
which links to this google…
-
TL;DR: We don't need service endpoints in the DID Document... it's an overly-complicated anti-pattern that has a lot of downsides when we already have patterns that are implemented today that would wo…