Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion eng/versioning/version_client.txt
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ com.azure:azure-developer-loadtesting;1.0.32;1.2.0-beta.2
com.azure:azure-digitaltwins-core;1.5.9;1.6.0-beta.1
com.azure:azure-health-deidentification;1.0.0;1.1.0-beta.2
com.azure:azure-health-insights-radiologyinsights;1.1.10;1.2.0-beta.1
com.azure:azure-identity;1.18.7;1.19.0-beta.3
com.azure:azure-identity;1.18.7;1.19.0
com.azure:azure-identity-extensions;1.2.10;1.3.0-beta.1
com.azure:azure-identity-broker;1.1.24;1.2.0-beta.1
com.azure:azure-identity-broker-samples;1.0.0-beta.1;1.0.0-beta.1
Expand Down
2 changes: 1 addition & 1 deletion sdk/identity/azure-identity-broker-samples/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-identity</artifactId>
<version>1.19.0-beta.3</version> <!-- {x-version-update;com.azure:azure-identity;current} -->
<version>1.19.0</version> <!-- {x-version-update;com.azure:azure-identity;current} -->
</dependency>
<dependency>
<groupId>com.azure</groupId>
Expand Down
2 changes: 1 addition & 1 deletion sdk/identity/azure-identity-broker/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@
<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-identity</artifactId>
<version>1.19.0-beta.3</version> <!-- {x-version-update;com.azure:azure-identity;current} -->
<version>1.19.0</version> <!-- {x-version-update;com.azure:azure-identity;current} -->
</dependency>

<dependency>
Expand Down
2 changes: 1 addition & 1 deletion sdk/identity/azure-identity-perf/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-identity</artifactId>
<version>1.19.0-beta.3</version> <!-- {x-version-update;com.azure:azure-identity;current} -->
<version>1.19.0</version> <!-- {x-version-update;com.azure:azure-identity;current} -->
</dependency>
<dependency>
<groupId>com.azure</groupId>
Expand Down
30 changes: 20 additions & 10 deletions sdk/identity/azure-identity/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,27 +1,37 @@
# Release History

## 1.19.0-beta.3 (Unreleased)
## 1.19.0 (2026-10-29)

### Features Added

- Added support for user-assigned managed identities on Azure Arc in `ManagedIdentityCredential` and `DefaultAzureCredential`.

### Breaking Changes
- Added `enableAzureProxy()` method to `WorkloadIdentityCredentialBuilder` to 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](https://github.com/Azure/azure-sdk-for-java/pull/50917))

### Bugs Fixed

- Disabled MSAL's internal retry for Confidential Client, Managed Identity and Public Client Applications. ([#48472](https://github.com/Azure/azure-sdk-for-java/pull/48472))
- Fixed misleading authentication error reporting when token requests are interrupted or the JVM shuts down. ([#50585](https://github.com/Azure/azure-sdk-for-java/issues/50585))
- Fixed IMDS discovery in `DefaultAzureCredential` to wait for HTTP response headers with a read timeout, allowing the credential chain to continue when a local endpoint accepts connections but does not respond, while preserving fallback on probe setup failures. ([#50517](https://github.com/Azure/azure-sdk-for-java/pull/50517))
- Fixed `OnBehalfOfCredential` token 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](https://github.com/Azure/azure-sdk-for-java/pull/50618))

### Other Changes

- Improved `AzureDeveloperCliCredential` error handling to extract meaningful messages from `azd auth token` JSON output, providing cleaner error messages to users.
- Upgraded `azure-core` from `1.60.0` to version `1.61.0`.
- Upgraded `azure-core-http-netty` from `1.16.8` to version `1.17.0`.

#### Dependency Updates
---
Comment thread
vcolin7 marked this conversation as resolved.
Resolved

- Upgraded `msal4j` from `1.23.1` to `1.26.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_NAME` being 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](https://github.com/Azure/azure-sdk-for-java/pull/50917))
- Fixed the AKS token proxy accepting CA bundles containing a valid certificate followed by a malformed certificate entry. ([#50917](https://github.com/Azure/azure-sdk-for-java/pull/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](https://github.com/Azure/azure-sdk-for-java/pull/50917))
- Fixed a race between proxy CA reloads and socket factory creation that could leave requests using the previous CA configuration. ([#50917](https://github.com/Azure/azure-sdk-for-java/pull/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](https://github.com/Azure/azure-sdk-for-java/pull/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](https://github.com/Azure/azure-sdk-for-java/pull/50917))
- Fixed the proxy transport leaking into subsequent credentials built with the same `WorkloadIdentityCredentialBuilder` after proxy settings were removed. Proxy options are now applied to a per-credential copy instead of mutating the builder. ([#50917](https://github.com/Azure/azure-sdk-for-java/pull/50917))

### Other Changes

- Added AKS identity binding usage guidance and an opt-in example for `WorkloadIdentityCredentialBuilder.enableAzureProxy()`. ([#50917](https://github.com/Azure/azure-sdk-for-java/pull/50917))

## 1.18.7 (2026-10-01)

Expand Down
48 changes: 47 additions & 1 deletion sdk/identity/azure-identity/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ To take dependency on a particular version of the library that isn't present in
<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-identity</artifactId>
<version>1.18.4</version>
<version>1.19.0</version>
</dependency>
```
[//]: # ({x-version-update-end})
Expand Down Expand Up @@ -146,6 +146,52 @@ public void createDefaultAzureCredentialForVSCode() {
}
```

### Authenticate with AKS identity bindings

[Azure Kubernetes Service (AKS) identity bindings](https://learn.microsoft.com/azure/aks/identity-bindings-concepts)
let multiple clusters share a user-assigned managed identity through a single AKS-managed federated identity
credential, avoiding the limit of 20 federated identity credentials per managed identity.

Use `WorkloadIdentityCredential` directly and call `enableAzureProxy()` to route authentication through the AKS token
proxy. This option is disabled by default and isn't supported by `DefaultAzureCredential` or `ManagedIdentityCredential`.

The identity binding API requires `azure-identity` `1.19.0-beta.2` or a later version containing this feature.
It isn't included in `1.18.x` packages. If your BOM selects a `1.18.x` version, override it with an identity binding-enabled
version.

```java readme-sample-workloadidentitybinding
WorkloadIdentityCredential credential = new WorkloadIdentityCredentialBuilder()
.enableAzureProxy()
.build();
```

First [configure the AKS identity binding and Kubernetes permissions](https://learn.microsoft.com/azure/aks/identity-bindings).
The pod must use an authorized service account and have the `azure.workload.identity/use: "true"` label and
`azure.workload.identity/use-identity-binding: "true"` annotation. For Jobs and Deployments, set these on the pod template.
The workload identity webhook provides the configuration:

| Environment variable | Purpose |
| --- | --- |
| `AZURE_CLIENT_ID` | Client ID of the user-assigned managed identity, not its object ID. |
| `AZURE_TENANT_ID` | Microsoft Entra tenant ID. |
| `AZURE_FEDERATED_TOKEN_FILE` | Projected Kubernetes service account token file. |
| `AZURE_AUTHORITY_HOST` | Microsoft Entra authority. Keep this set to the authority, not the proxy URL. |
| `AZURE_KUBERNETES_TOKEN_PROXY` | HTTPS token proxy endpoint. It must not contain credentials, query parameters, or a fragment. |
| `AZURE_KUBERNETES_SNI_NAME` | TLS server name used to verify the proxy certificate. |
| `AZURE_KUBERNETES_CA_FILE` or `AZURE_KUBERNETES_CA_DATA` | Trusted CA bundle, either a file path or inline PEM text. Don't set both or Base64 encode the inline text. |

The credential reloads changes to a CA file on subsequent network requests. A temporarily missing or empty file during
rotation retains the previously loaded CA; an invalid nonempty bundle fails authentication. If neither CA setting is
provided, the platform trust store is used.

Enabling the option without any proxy settings uses the direct workload identity flow. Partial or invalid proxy
configuration fails instead of silently falling back to direct authentication. With proxy configuration present,
a dedicated HTTP transport is set on a copy of the credential options. A custom HTTP pipeline retains its usual
precedence over HTTP client settings.

An identity binding authorizes token acquisition, not access to Azure resources. Assign Azure roles to the managed
identity separately when resource access is required.

## Managed Identity support

The [Managed identity authentication](https://learn.microsoft.com/entra/identity/managed-identities-azure-resources/overview) is supported indirectly via `DefaultAzureCredential` or directly via `ManagedIdentityCredential` for the following Azure Services:
Expand Down
4 changes: 3 additions & 1 deletion sdk/identity/azure-identity/TROUBLESHOOTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -273,7 +273,9 @@ Get-AzAccessToken -ResourceUrl "https://management.core.windows.net"
|---|-------------------------------------------------------------------------------------------------------------------------------|---|
|`CredentialUnavailableException` raised with message. "WorkloadIdentityCredential authentication unavailable. The workload options are not fully configured."| The `WorkloadIdentityCredential` requires `clientId`, `tenantId` and `tokenFilePath` to authenticate with Microsoft Entra ID. | <ul><li>If using `DefaultAzureCredential` then:</li><ul><li>Ensure client ID is specified via `workloadIdentityClientId` setter or `AZURE_CLIENT_ID` env variable.</li><li>Ensure tenant ID is specified via `AZURE_TENANT_ID` env variable.</li><li>Ensure token file path is specified via `AZURE_FEDERATED_TOKEN_FILE` env variable.</li><li>Ensure authority host is specified via `AZURE_AUTHORITY_HOST` env variable.</ul><li>If using `WorkloadIdentityCredential` then:</li><ul><li>Ensure tenant ID is specified via `tenantId` setter on credential builder or `AZURE_TENANT_ID` env variable.</li><li>Ensure client ID is specified via `clientId` setter on the credential builder or `AZURE_CLIENT_ID` env variable.</li><li>Ensure token file path is specified via `tokenFilePath` setter on the credential builder or `AZURE_FEDERATED_TOKEN_FILE` environment variable. </li></ul></li><li>Consult the [product troubleshooting guide](https://azure.github.io/azure-workload-identity/docs/troubleshooting.html) for other issues.</li></ul>
|`CredentialUnavailableException` raised with message. "WorkloadIdentityCredential authentication unavailable. The request to the authority host was invalid."| The configured properties for workload identity are invalid. | Ensure the properties for workload identity are correctly configured on the credential builder and right permissions are assigned to the workload identity.
|In an application using [Azure Kubernetes Service identity bindings](https://learn.microsoft.com/azure/aks/identity-bindings-concepts): <ul><li>AADSTS700211: No matching federated identity record found for presented assertion issuer ...</li><li>AADSTS700212: No matching federated identity record found for presented assertion audience 'api://AKSIdentityBinding'.</li></ul> |`WorkloadIdentityCredential` isn't configured to use the identity binding proxy|Call `WorkloadIdentityCredentialBuilder.enableAzureProxy()` while building the credential.
|In an application using [Azure Kubernetes Service identity bindings](https://learn.microsoft.com/azure/aks/identity-bindings-concepts): <ul><li>AADSTS700211: No matching federated identity record found for presented assertion issuer ...</li><li>AADSTS700212: No matching federated identity record found for presented assertion audience 'api://AKSIdentityBinding'.</li></ul> |`WorkloadIdentityCredential` isn't configured to use the identity binding proxy, or its binding and permissions aren't configured.|Use `WorkloadIdentityCredential` directly and call `WorkloadIdentityCredentialBuilder.enableAzureProxy()`. Confirm that the webhook supplied `AZURE_KUBERNETES_TOKEN_PROXY` and the pod uses an authorized service account. `DefaultAzureCredential` and `ManagedIdentityCredential` don't support identity binding mode.|
|Invalid AKS proxy configuration.|The proxy URL is missing or invalid, both CA sources are configured, or inline CA data is empty.|Use an absolute HTTPS proxy URL without credentials, a query, or a fragment. Set at most one of `AZURE_KUBERNETES_CA_FILE` and `AZURE_KUBERNETES_CA_DATA`; inline data must be PEM text, not Base64. Keep `AZURE_AUTHORITY_HOST` set to the Microsoft Entra authority.|
|TLS failure when connecting to the AKS token proxy.|The proxy certificate isn't trusted or doesn't match `AZURE_KUBERNETES_SNI_NAME`.|Check the webhook's CA and TLS server-name settings. Ensure the CA file exists on first use. Missing or empty files during rotation retain an already loaded CA, but invalid nonempty bundles fail authentication. Never disable TLS verification.|

## Troubleshoot `IntelliJCredential` authentication issues

Expand Down
2 changes: 1 addition & 1 deletion sdk/identity/azure-identity/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@

<groupId>com.azure</groupId>
<artifactId>azure-identity</artifactId>
<version>1.19.0-beta.3</version><!-- {x-version-update;com.azure:azure-identity;current} -->
<version>1.19.0</version><!-- {x-version-update;com.azure:azure-identity;current} -->

<name>Microsoft Azure client library for Identity</name>
<description>This module contains client library for Microsoft Azure Identity.</description>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -22,19 +22,18 @@
import static com.azure.identity.ManagedIdentityCredential.AZURE_FEDERATED_TOKEN_FILE;

/**
* <p>Workload Identity authentication is a feature in Azure that allows applications running on virtual machines (VMs)
* to access other Azure resources without the need for a service principal or managed identity. With Workload Identity
* authentication, applications authenticate themselves using their own identity, rather than using a shared service
* principal or managed identity. Under the hood, Workload Identity authentication uses the concept of Service Account
* Credentials (SACs), which are automatically created by Azure and stored securely in the VM. By using Workload
* Identity authentication, you can avoid the need to manage and rotate service principals or managed identities for
* each application on each VM. Additionally, because SACs are created automatically and managed by Azure, you don't
* need to worry about storing and securing sensitive credentials themselves.
* The WorkloadIdentityCredential supports Azure workload identity authentication on Azure Kubernetes and acquires
* a token using the service account credentials available in the Azure Kubernetes environment.
* <p>Authenticates workloads on Kubernetes by exchanging a projected service account token for a Microsoft Entra
* access token. The identity's federated identity credential defines which service account tokens are trusted,
* without requiring the application to manage a secret or certificate.
* Refer to <a href="https://learn.microsoft.com/azure/aks/workload-identity-overview">Microsoft Entra Workload ID</a>
* for more information.</p>
*
* <p>Azure Kubernetes Service (AKS) identity bindings allow multiple clusters to share a user-assigned managed identity
* through a single AKS-managed federated identity credential. To route token exchanges through the AKS token proxy,
* call {@link WorkloadIdentityCredentialBuilder#enableAzureProxy()} when constructing this credential.
* Identity binding mode is disabled by default and is not supported by {@link DefaultAzureCredential} or
* {@link ManagedIdentityCredential}. The binding and Kubernetes permissions must be configured separately.</p>
*
* <p><strong>Sample: Construct WorkloadIdentityCredential</strong></p>
*
* <p>The following code sample demonstrates the creation of a {@link WorkloadIdentityCredential},
Expand Down
Loading
Loading