Skip to content
Merged
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
30 changes: 25 additions & 5 deletions changelog.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,28 @@
## Unreleased

### Bug fixes
- Move Credential Guard key attestation into the optional `Microsoft.Identity.Web.KeyAttestation` package. Managed identity mTLS proof-of-possession uses the unattested flow unless the package is installed and `AddMicrosoftIdentityWebKeyAttestation()` is registered, preventing native key-attestation binaries and symbols from being published with unrelated applications.
- OWIN web APIs now require bearer tokens to contain a recognized scope or role claim with a non-whitespace value by default. ACL-based authorization remains available by setting `AllowWebApiToBeAuthorizedByACL` to `true`.
## 4.15.0

### Federated credentials and proof of possession
- Federated credential token exchange now derives its audience and scope from the authority host, enabling sovereign and private cloud scenarios without requiring application code for the common case. Explicit metadata overrides remain supported. See [#3994](https://github.com/AzureAD/microsoft-identity-web/pull/3994).
- The Entra Sidecar `/Validate` endpoint now accepts Signed HTTP Request proof-of-possession tokens for app-only client-credential flows. Existing bearer-token validation remains unchanged. See [#4008](https://github.com/AzureAD/microsoft-identity-web/pull/4008).
- Credential Guard key attestation is now provided by the optional `Microsoft.Identity.Web.KeyAttestation` package. Applications that require attestation install the package and register `AddMicrosoftIdentityWebKeyAttestation()`; other applications no longer receive its native dependencies. See [#4004](https://github.com/AzureAD/microsoft-identity-web/pull/4004).

### Authentication and token acquisition
- EasyAuth `GetAuthenticationResultForAppAsync` now uses client-credential acquisition and returns an app-only authentication result instead of the provider token associated with the signed-in user. See [#4015](https://github.com/AzureAD/microsoft-identity-web/pull/4015).
- Graph v4 credentials are attached only to absolute HTTPS destinations matching the configured client origin, including after request customization. Custom Graph proxies remain supported through the client's absolute HTTPS base URL. See [#4012](https://github.com/AzureAD/microsoft-identity-web/pull/4012).

### Authorization and request validation
- OWIN web APIs require bearer tokens to contain a recognized scope or role claim with a non-whitespace value. Applications using ACL-based authorization must set `AllowWebApiToBeAuthorizedByACL` to `true`. See [#4006](https://github.com/AzureAD/microsoft-identity-web/pull/4006) and [#4009](https://github.com/AzureAD/microsoft-identity-web/pull/4009).
- Authorization fails when an explicitly configured scope or app-permission key is missing. Applications must provide the referenced configuration value or remove the explicit requirement. See [#4010](https://github.com/AzureAD/microsoft-identity-web/pull/4010).
- Local redirect paths containing control characters are rejected. See [#4028](https://github.com/AzureAD/microsoft-identity-web/pull/4028).

### Entra Sidecar reliability and validation
- Requests with a selected `AgentUserId` that is empty, malformed, or the empty GUID now return HTTP 400. Callers can provide a non-empty GUID or omit the user ID. See [#4011](https://github.com/AzureAD/microsoft-identity-web/pull/4011).
- Outside Development, startup rejects automatic forwarded-header processing when `ForwardedHeaders_Enabled` is `true`. See [#4018](https://github.com/AzureAD/microsoft-identity-web/pull/4018).
- Outside Development, non-local `Host` headers are rejected on all endpoints except `/healthz`. Supported local hosts are `localhost`, `127.0.0.1`, and `[::1]`. See [#4023](https://github.com/AzureAD/microsoft-identity-web/pull/4023).
- Windows container startup now uses the built-in `ContainerUser` account, and ACL authorization defaults are correctly applied to named bearer options. See [#4042](https://github.com/AzureAD/microsoft-identity-web/pull/4042).

### Dependency updates
- Update `Microsoft.Identity.Client` and `Microsoft.Identity.Client.KeyAttestation` from 4.87.0 to 4.90.0. See [#4003](https://github.com/AzureAD/microsoft-identity-web/pull/4003), [#3994](https://github.com/AzureAD/microsoft-identity-web/pull/3994), and [#4052](https://github.com/AzureAD/microsoft-identity-web/pull/4052).
- Update `Microsoft.Identity.Abstractions` from 12.6.0 to 12.7.0. See [#4020](https://github.com/AzureAD/microsoft-identity-web/pull/4020) and [#3994](https://github.com/AzureAD/microsoft-identity-web/pull/3994).

## 4.14.2

Expand Down
Loading