Closed cveld closed 5 years ago
@cveld Thanks for your feedback! We will investigate and update as appropriate.
@cveld This is where the app service platform will be looking at by default, which is why the doc suggests to place the jwt in the x-zumo header.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
@BryanTrach-MSFT maybe you can explain the origin of the name? "aZUre MObile"? And maybe you can explain the preference for such a custom header. Wouldn't it be more logical to add bearer handling to Easy Auth as well?
@BryanTrach-MSFT X-ZUMO-AUTH
doesn't work if the provider is AAD and the target is Azure Function api. But Authorization
header works.
Why do you suggest to put the jwt in the custom http header "x-zumo-auth"? Wouldn't you prefer to use the authorization bearer header?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.