Releases: softawaregmbh/library-authentication
SAS Token Autentication
This release adds support for SAS (Shared Access Signature) token authentication.
See the README for more details.
.NET8.0
Support multiple hashing algorithms, drop .NET 4.6.1 support
New Features
- Hash algorithm in header by @meinsiedler in #17
- The default request body hashing method is now SHA-256.
Breaking Changes
- Drop support for .NET 4.6.1 by @meinsiedler in #16
ApiKeyDelegatingHandler
constructor with inner delegating handler: Order of parameters changed. The innerHttpMessageHandler
is now the first constructor parameter.
Upgrade guide
With #17 it is now possible to specify the hashing algorithm to be used. If you have used this library in an older version before, we recommend the following upgrade path:
- Update the server's NuGet package softaware.Authentication.Hmac.AspNetCore to latest version. This version is backwards compatible with an older version of the client.
- Update the client's NuGet package softaware.Authentication.Hmac.Client to latest version after the server has been deployed with the latest version. This version now uses SHA-256 request body hashing by default.
With this approach, no breaking changes occur at the deployed environment as the backwards compatibility is ensured.
Full Changelog: 3.4.0-hmac...4.0.0
HMAC 3.4.0: SHA-256 support for request body hashing
This release prepares for upgrading the request body hashing from MD5 to SHA-256.
This is an intermediate release for upgrading the library without breaking changes. The new options will be removed again in the next major release and only SHA-256 will be supported in future.
New Features
softaware.Authentication.Hmac.AspNetCore
- New Option
AllowMD5AndSHA256RequestBodyHash
inHmacAuthenticationSchemeOptions
: Iftrue
, the request body hash will be validated with MD5 hash and SHA265 hash. Note that this setting is only relevant when the http request has a body. (Default:true
)
softaware.Authentication.Hmac.Client
- The
ApiKeyDelegatingHandler
now supports passing a new enumRequestBodyHashingMethod
to the constructor to set the hash algorithm to be used for the request body hashing. Possible options areMD5
andSHA256
Upgrade guide
- Upgrade the
softaware.Authentication.Hmac.AspNetCore
to support both MD5 and SHA-256. - Deploy the server part.
- The client still sends request with MD5 hash which will be accepted by server.
- Update the
softaware.Authentication.Hmac.Client
and set theRequestBodyHashingMethod
toSHA256
.- The server will accept SHA-256 hashes too.
The next major releases will support SHA-256 only.
What's Changed
- Use SHA256 for request body hashing by @meinsiedler in #15
Full Changelog: 3.3.0-hmac...3.4.0-hmac
3.3.0 HMAC
What's Changed
- Update documentation by @rschacherl in #10
- Fix request scheme behind proxy by @funcmike in #11
New Contributors
- @rschacherl made their first contribution in #10
- @funcmike made their first contribution in #11
Full Changelog: 3.1.0...3.3.0-hmac
3.2.0 HMAC
Add IHmacAuthorizationProvider
interface to allow custom implementations for getting HMAC apps. (#6)
3.1.0
New Features
- This release adds support for
netstandard2.0
for the projectssoftaware.Authentication.Basic.AspNetCore
andsoftaware.Authentication.Basic.AspNetCore
and removes the depdendency tonetcoreapp3.1
. - On successful authentication, the
ClaimsIdentity
now contains a claim of typeNameIdentitifier
. For basic authentication, this is the username, for HMAC authentication, this is the AppId.
3.0.0
This release adds support for .NET Core 3.1 and drops the support for .NET 4.6.2 for the ASP.NET Core packages softaware.Authentication.Hmac.AspNetCore
and softaware.Authentication.Basic.AspNetCore
.
If you want to support .NET Core 2.2 or .NET 4.6.2 use the previous version of this package.
1.1.0
- This release adds support for Source Link.
- The dependencies and tests are fixed for .NET 4.6.1 target
1.0.1
Updated NuGet package metadata