Releases: AzureAD/microsoft-identity-abstractions-for-dotnet
Releases · AzureAD/microsoft-identity-abstractions-for-dotnet
9.2.0: changelog.md with recent changes since May 17th (#197)
9.2.0
New features
-
OperationResult and OperationError abstractions:
Introduced a newOperationResult<TResult, TError>
struct andOperationError
base class. These provide a discriminated union for representing either a result or an error, improving error handling and propagation.
See implementation insrc/Microsoft.Identity.Abstractions/Results/OperationResult.cs
andOperationError.cs
. -
DownstreamApiOptions extensibility:
Added two new properties toDownstreamApiOptions
:ExtraHeaderParameters
(IDictionary<string, string>?
): Set extra headers in HTTP requests to downstream APIs.ExtraQueryParameters
(IDictionary<string, string>?
): Set extra query parameters in HTTP requests to downstream APIs.
This enables more flexible API calls and improved integration scenarios.
Fundamentals
-
Development guidelines and Copilot integration:
- Introduced
.clinerules/abstractions-guidelines.md
,.clinerules/csharp-guidelines.md
,.clinerules/ai-guidelines.md
, and.github/copilot-instructions.md
to formalize and document development, AI assistant, and C# code standards for contributors and tooling. - Solution file and README updated to reference these guidelines.
- Introduced
-
Analyzer and dependency updates:
- Bumped analyzer versions in
Directory.Build.props
for better static analysis (BannedApiAnalyzers and MicrosoftCodeAnalysisPublicApiAnalyzers updated from 3.3.4 to 4.14.0).
- Bumped analyzer versions in
9.1.0: Update Directory.Build.props (#188)
9.1.0
New features
- Add a new generic IAuthorizationHeaderProvider to have the possiblity of returning authorization header and metadata or error instead of throwing. For details see #172
- Add Algorithm property to CredentialDescription to describe signing credentials. For details see #182
- Adding serializer for CredentialDescription in .NET 8+. See #176
Fundamentals
9.0.0
9.0.0
New features
- Added a new class named
MicrosoftEntraApplicationOptions
inheriting fromIdentityApplicationOptions
and from whichMicrosoftIdentityApplicationOptions
inherits. Moved the EntraID specific properties related to web APIs fromMicrosoftIdentityApplicationOptions
toMicrosoftEntraApplicationOptions
.MicrosoftIdentityApplicationOptions
now only contains the
properties related to web apps and B2C. See #165 for details. - Added a
Name
property inMicrosoftEntraApplicationOptions
to allow for dynamic discovery of ASP.NET Core authentication schemes / named options. See #168 for details. - Changed the way the ID property is computed in ClientCredentials. All sensitive data is also now replaced by a hash. See #163 for details.
- Added XML comments with recommendations on which CredentialSource not to use in production. See #167 for details.
8.2.0
8.1.1
8.1.0
8.1.0
New features:
- To support certain Federation identity cases, you need to add an additional parameter called
TokenExchangeAuthority
. This parameter is necessary when the issuer (the entity that issues the token) for the token exchange URL is different from the application's issuer. See #155 for details. - Added a new interface
ICustomSignedAssertionProvider
for implementing custom signed assertion providers. This interface includes aName
property for configuration-friendly naming. See issue #153 for details. - Added extensibility to the
CredentialDescription
class to support custom signed assertion providers. This includes new propertiesCustomSignedAssertionProviderName
andCustomSignedAssertionProviderData
. See issue #146 for details.
What's Changed
- Update changelog.md for 8.0.0 and other post release updates by @jmprieur in #152
- Add customSignedAssertion by @JoshLozensky in #150
- Adding ICustomSignedAssertionProvider by @JoshLozensky in #154
- done with copilot by @jennyf19 in #156
Full Changelog: 8.0.0...8.1.0
8.0.0
7.2.1
7.2.1
Bug fix:
Id
property inCredentialDescription
was derived from secret values, primarily affecting logging (information level) of credential attempts inMicrosoft.Identity.Web
, it doesn't affect higher log levels because if the failure occurs, it indicates that a credential description has both a credential source that can fail (e.g., certificate) and theClientSecret
property set, which is not a typical scenario. See issue #147 for details.
7.2.0
7.2.0
New features:
- Add
AppHomeTenantId
toMicrosoftIdentityApplicationOptions
to allow multi-tenant applications to specify theAppHomeTenantId
to be used for client credentials. See PR #142 and Id Web for details.
What's Changed
- Post release 7.1.0 - Update version to next and move unshipped public API to shipped by @jmprieur in #141
- Add AppHomeTenantId to MicrosoftIdentityApplicationOptions by @msbw2 in #142
- Update changelog.md by @jennyf19 in #143
New Contributors
Full Changelog: 7.1.0...7.2.0