Support For Asymmetric Signatures on Client Libraries
J0 opened this issue · comments
Hi,
I'm hoping to use Standard Webhooks for an internal project at Supabase. I was glancing through the repository after reading the specification and noticed that the JavaScript and Go libraries currently use symmetric verification and signing and that there doesn't seem to be an implementation for asymmetric verification and signing via ed25519 as per spec.
Can I check if this is something that's on the roadmap within the next three weeks and/or something that the committee would be open to accepting contributions on?
Let me know
Thanks for opening this ticket! Yeah, it's waiting on #34 which may require a tiny improvement before it goes into the libs.
Hey @tasn,
Sorry to bother you but wanted to check in and see where we've landed with respect to the recommended signing method for asymmetric signatures. Is there anything that I could do which would be helpful in moving asymmetric signatures along?
If it'd be at all helpful I'm happy to help with the implementation of the client library bindings if it would move things along.
Lmk!
Sorry, I still haven't gotten to it. Adding a calendar block for myself for this week.