Microsoft Kiota Authentication Azure Library for Python
The Microsoft Kiota Authentication Azure Library is an implementation to authenticate HTTP requests using @azure/identity.
A Kiota generated project will need a reference to an authentication provider to make calls to an API endpoint.
Read more about Kiota here.
Using the Microsoft Kiota Authentication Azure library
In order to use this library, install the package by running:
pip install microsoft-kiota-authentication-azure
The application owns the credential passed to AzureIdentityAccessTokenProvider.
The provider leaves it open so it can be reused for token refreshes, concurrent
requests, or multiple clients. Close the credential after all clients using it
have finished. For async Azure Identity credentials, use an async with context
manager around the client lifetime or call await credential.close() at shutdown.
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Trademarks
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
2 maintainers
Metadata
2 maintainers
Release files for microsoft-kiota-authentication-azure 1.16.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| microsoft_kiota_authentication_azure-1.16.0.tar.gz | 5.5 kB | Without provenance | Details for microsoft_kiota_authentication_azure-1.16.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| microsoft_kiota_authentication_azure-1.16.0-py3-none-any.whl | Python 3 | none | any | Details for microsoft_kiota_authentication_azure-1.16.0-py3-none-any.whl |
Total release size: 13.0 kB
Release files / microsoft_kiota_authentication_azure-1.16.0.tar.gz
| Download URL | microsoft_kiota_authentication_azure-1.16.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7a1aeb8d1e8820c3a624e277a6587dc7078cd06c5c6af9d0e67f7f63fbe645a
|
|
BLAKE2b-256 checksum How to use checksums |
9ab0cd322067e9a8b17c20dbfd0a65fba1e1986ea4d340e16c85520fb8afbb52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
RestSharp/106.13.0.0
|
Release files / microsoft_kiota_authentication_azure-1.16.0-py3-none-any.whl
| Download URL | microsoft_kiota_authentication_azure-1.16.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52ed4f507a2d028a88d685f14099dec68228ee8919e697d5a514419c3b479f76
|
|
BLAKE2b-256 checksum How to use checksums |
09ee2aceb887c5b7c8873cbb8ce483b361c0cf4b8a7bf26cab2770120a2efb38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
RestSharp/106.13.0.0
|
Security for microsoft-kiota-authentication-azure 1.16.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
