1.19.0 (2026-10-29)
Features Added
- Added
enableAzureProxy()method toWorkloadIdentityCredentialBuilderto enable custom token proxy support for Azure Kubernetes clusters. When enabled, the credential attempts to use a custom token proxy configured through environment variables (AZURE_KUBERNETES_TOKEN_PROXY,AZURE_KUBERNETES_CA_FILE,AZURE_KUBERNETES_CA_DATA,AZURE_KUBERNETES_SNI_NAME). (#50917)
Bugs Fixed
- Fixed
OnBehalfOfCredentialtoken cache lookup to remain bound to the configured user assertion, preventing a cached token acquired for one user from being returned for another user with matching scopes. (#50618)
Other Changes
- Updated credential builder documentation to clarify that providing managed identity ID options select a user-assigned identity, while omitting them selects the system-assigned identity. (#51021)
Dependency Updates
- Upgraded
azure-corefrom1.60.0to version1.61.0. - Upgraded
azure-core-http-nettyfrom1.16.8to version1.17.0.
The updates below only denote differences between this release and previous 1.19.0 beta releases, not the 1.18.x stable implementation.
Bugs Fixed
- Fixed verification of
AZURE_KUBERNETES_SNI_NAMEbeing skipped when the proxy certificate already matched the proxy URL hostname. The configured name is now checked during TLS handshakes, including connections opened by automatic HTTP retries, before sending the service-account assertion. Certificate DNS wildcards that match exactly one label remain supported. (#50917) - Fixed the AKS token proxy accepting CA bundles containing a valid certificate followed by a malformed certificate entry. (#50917)
- Fixed authentication failures when a previously loaded proxy CA file temporarily disappears during rotation. The existing fallback for an empty CA file is unchanged. (#50917)
- Fixed a race between proxy CA reloads and socket factory creation that could leave requests using the previous CA configuration. (#50917)
- Fixed blocking I/O in the internal AKS proxy transport's reactive send and response-body APIs running on subscriber threads. These operations now use a blocking-I/O scheduler. Synchronous body reads, including those used by the MSAL bridge, stay on the calling thread to avoid starvation when that scheduler is saturated. (#50917)
- Fixed the AKS token proxy converting I/O failures while opening response streams for HTTP statuses below 400 into empty bodies. These failures now propagate. HTTP error responses without a body still retain their error status. (#50917)
- Fixed the proxy transport leaking into subsequent credentials built with the same
WorkloadIdentityCredentialBuilderafter proxy settings were removed. Proxy options are now applied to a per-credential copy instead of mutating the builder. (#50917)
Other Changes
- Added AKS identity binding usage guidance and an opt-in example for
WorkloadIdentityCredentialBuilder.enableAzureProxy(). (#50917)