You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
1.10.0 (2024-10-08)
Features Added
Added support for providing an object ID or a resource ID to ManagedIdentityCredential.
Added support for passing in the x509 certificate and its corresponding private key directly to ClientCertificateCredential, rather than reading from a pem file.
Added support for sending an x5c parameter in ClientCertificateCredential.
Breaking Changes
Previously, if a clientId was specified for Cloud Shell managed identity, which is not supported, the clientId was passed into the request body. Now, an exception will be thrown if a clientId is specified for Cloud Shell managed identity.
Bugs Fixed
Fixed the request sent in AzurePipelinesCredential so it doesn't result in a redirect response when an invalid system access token is provided.
Other Changes
Allow certain response headers to be logged in AzurePipelinesCredential for diagnostics and include them in the exception message.
In ClientCertificateCredential, add the x5c parameter of the JWT token as a JSON array rather than a JSON string.