Azure Core providing authentication policies and using these in generated crates - Githubissues

Azure / azure-sdk-for-rust

This repository is for active development of the *unofficial* Azure SDK for Rust. This repository is *not* supported by the Azure SDK team.

MIT License

680 stars 232 forks source link

Azure Core providing authentication policies and using these in generated crates #1595

Open krishanjmistry opened 5 months ago

krishanjmistry commented 5 months ago

I noticed that #360 was closed recently, I'd have assumed part of this would have been adding a BearerTokenAuthenticationPolicy as per Azure Core guidelines: https://azure.github.io/azure-sdk/general_azurecore.html#authentication-policy

[ ] Provide a BearerTokenAuthenticationPolicy in Azure Core
[ ] Replace existing uses of BearerTokenAuthenticationPolicy in hand-written crates (I believe this is primarily Key Vault)
[ ] Replace authentication within generated crates to use a Pipeline policy for authentication rather than including in the base request

Thinking forward, I'm unsure on:

how this would work for generated clients that have custom authentication requirements (e.g. storage accepting SAS tokens)
how it might be possible to generate hand written clients on top of the generated crates requests (not just the models)