microsoft / microsoft/azurechat
Costum extention Autorization header
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
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 !
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing ClientsCredential authorization flow and the Azure Function proxy workaround described in the issue; no repository file or test is named. Clarify whether a static extension should produce an Authorization header containing the bearer token and email SHA-256, then verify the resulting header against a secured API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- api, authentication, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100