I've started working on generating RFC9421 compatible HTTP-Signatures in # GoActivityPub about a week and a half ago, but it felt more like a month

submitted by

I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

#ActivityPubDev #fedidev #httpsig

2
4

Log in to comment

Hot Top New Old
OP

As always, as I start the work for the verifier in the auth module, the coverage is quite low:

coveralls.io/github/go-ap/auth

 reply
1
OP

The work is done, huzzah!! 🥳

With the coverage increased to +85% and with a couple of pending improvements to the common-fate/httpsig library. Until those land, I'm using a forked version.

The auth module has transformed during this work to only have logic related to extracting authorized actors from either OAuth2 and HTTP-Signature headers (both the widely used draft and the new RFC9421 version).

This makes me confident that the convergence of the library's modules that I'm planning for v1 is actually a good idea.

 reply
1
Insert image