digitalbazaar / digitalbazaar/ezcap

Consider implementing CapabilityAgent from webkms-client

Open
#13 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
8
Forks
4
Avg merge
3h 5m
Merged PRs (30d)
1

Description

The CapabilityAgent class (or similar) may be more well suited to this library; it doesn't require any WebKMS constructs nor do WebKMS constructs directly require it. However, it is consistently and generally just used to generate an invocationSigner for signing zcaps.

https://github.com/digitalbazaar/webkms-client/blob/main/CapabilityAgent.js

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked webkms-client CapabilityAgent.js and then inspect ezcap's current capability-signing entry points. Done means ezcap provides a CapabilityAgent or equivalent that can generate an invocationSigner without requiring WebKMS constructs.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authorization
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.