I just realized that the key vault store the shs256 of an email and its make its so i can call a secured api with ClientsCredential work flow. I found a work around using a Azure Function as a proxy but i'm not yet a big fan of my own solution. Should i create a fork and do my own static extentions or theire is some plan of improvement.
At the end when the extentions is use , the header contain : Authorization : Bearer [my auth token], [my email sha256].
I just realized that the key vault store the shs256 of an email and its make its so i can call a secured api with ClientsCredential work flow. I found a work around using a Azure Function as a proxy but i'm not yet a big fan of my own solution. Should i create a fork and do my own static extentions or theire is some plan of improvement.
At the end when the extentions is use , the header contain : Authorization : Bearer [my auth token], [my email sha256].
Thx for any tips and tricks !