Edward Wilde

We are maintaining a fixed version of this library [https://github.com/form3tech-oss/jwt-go](https://github.com/form3tech-oss/jwt-go)  CVE fixed: [https://github.com/form3tech-oss/jwt-go/releases/tag/v3.2.1](https://github.com/form3tech-oss/jwt-go/releases/tag/v3.2.1) If that is of interest

- Read secrets?

Derek assign: ewilde

Derek assign: ewilde

Happy to go with `option 1`. However; looks like it would be a breaking change though, if I've understood the proposal correctly To create a new function resource you would...

@ameier38 we discussed this issue at our members meeting this evening on zoom. @alexellis suggested again the approach in the [above comment](https://github.com/openfaas/faas/issues/848#issuecomment-503047287). Openfaas-operator is already serialising the full function specification...

No progress made on this yet

@amitsaha as @jacktuck mentioned I'm not sure this approach would work for apis that are not idempotent. Perhaps we could include a response classifier section in the configuration similar to...

I've created a conceptual diagram for the http signatures flow: [diagram](https://github.com/ewilde/diagrams/blob/master/openfass%20http%20signature.svg)

Derek assign: ewilde