We need a 3rd option here, API key. This exists natively in Azure Functions (as ?code=... or X-FUNCTIONS-KEY header), while also being trivial to implement in own API (compare a stored secret with the value in the header). The UI should allow for custom named header, e.g.:
[ ] Basic
[ ] Certificate
[*] API key
HTTP header: [ input field ]
Value: [ input field ] // Would be really nice if this could be pulled out of Key Vault.
Also, who uses Basic Auth really? Come on.
We need a 3rd option here,
API key. This exists natively in Azure Functions (as?code=...orX-FUNCTIONS-KEYheader), while also being trivial to implement in own API (compare a stored secret with the value in the header). The UI should allow for custom named header, e.g.:Also, who uses Basic Auth really? Come on.