briandunnington

Any update on this? I see #1548 is also still open even though an Azure Functions PR that looks like it might have fixed it has been merged: https://github.com/Azure/azure-functions-host/pull/8129

Just wanted to confirm that @mrnewrochelle's suggestion worked for me. I had already tried installing gobally via npm and had the latest version (both via npm and VS) but was...

Appears to be the similar to #313 - I think the root cause is here: https://github.com/Azure/azure-functions-openapi-extension/blob/a1661dbec6c2e215c9f3bb3e9d0e2749ae731520/src/Microsoft.Azure.WebJobs.Extensions.OpenApi.Core/Extensions/TypeExtensions.cs#L579 (at least for the Dictionary case - likely a few lines down for the...

@brentschmaltz Yes, it is possible to 'roll my own' logic and do the signature verification by grabbing the key and doing it myself. But it would be nice if the...

@jennyf19 We ended up rolling our own implementation to replace the KeyVaultSignatureProvider implementation. In our implementation, we grab the key vault key and then do the verification locally instead of...