Dangl.Identity.Client 2.5.0

• .NETStandard 2.0

  • IdentityModel (>= 3.10.10)
  • Microsoft.Extensions.Logging.Abstractions (>= 2.2.0)

## v2.5.0:
- The generated assemblies now have a strong name. This is a breaking change of the binary API and will require recompilation on all systems that consume this package. The strong name of the generated assembly allows compatibility with other, signed tools. Please note that this does not increase security or provide tamper-proof binaries, as the key is available in the source code per [Microsoft guidelines](https://msdn.microsoft.com/en-us/library/wd40t7ad(v=vs.110).aspx)

## v2.4.3:
- Add `RequiredJwtRoles` and `RequiredJwtClaims` to `DanglIdentityServerConfiguration` to configure required claims and / or roles when using Jwt authentication

## v2.4.2:
- When `UseDanglIdentityJwtAuthentication` is enabled on servers, the integrated endpoints for cookie authentication are disabled
- CI tests for the .NET components are now also run on Linux

## v2.4.1:
- Include `Id` for current user in Angular client `AuthenticationMessenger`

## v2.4.0:
- Refactoring of Angular client

## v2.3.0:
- Update of **Dangl.Identity** dependencies
- Breaking Change: If you're using **Dangl.Identity** Jwt authentication from the **Dangl.Identity.Client.Mvc** package, you should set the property `UseDanglIdentityJwtAuthentication` in the configuration for **Dangl.Identity** to `true` and ensure that `app.UseDanglIdentityJwtTokenAuthentication()` is called early in your request pipeline

## v2.2.1:
- Bugfix where the Angular library failed to update the current authentication status after failed token refresh attempts

## v2.2.0:
- An Angular front end package is now available at `@dangl/angular-dangl-identity-client`

## v2.1.0:
- Update internal dependencies to latest **Dangl.Identity** and to ASP.NET Core 2.2

## v2.0.8:
- Update internal dependencies

## v2.0.7:
- Fix bug where invalid Jwt tokens led to internal server error responses in `Dangl.Identity.Client.Mvc`

## v2.0.4:
- Remove `HttpMessageHandler` constructor argument from `UserInformationTransmissionHttpHandler` to be better composable with `HttpClientFactory`
- Add overload to `UserInformationTransmissionHttpHandler` that allows to supply `IHttpContextAccessor` to be able to resolve dependencies on the fly from the `RequestServices`

## v2.0.3:
- Switch to `HttpClientFactory`
- Introduced `DanglIdentityHttpClientAccessor` to abstract accessing `HttpClient` in **Dangl.Identity.Client.Mvc** services

## v2.0.0:
- Add support for user identicon id properties
- Update to latest version 2.0.1 of `Dangl.Identity`
- Renamed `Dangl.Identity.OAuth` to `Dangl.Identity.Client.Mvc`

## v1.2.2:
- Fix deserialization error of Jwt `Bearer` tokens to no longer throw exceptions on invalid input in **Dangl.Identity.Client.Mvc**

## v1.2.1:
- `Dangl.Identity.Client` is now public

## v1.2.0:
- Add support for client-side integration of OpenID with **Dangl.Identity** as OpenID provider
- Add `UserInformationTransmissionHttpHandler` to share user information for requests contexts across different services
- `IUserService` will now also determine user ids and whether users are authenticated in inter-service calls
- See the README for requirements & setup on how to transmit user ids in inter-service requests
- The extensions for OAuth as server-side integration now only support either Cookie auth or Jwt, not both. Specifying one will disable the other

## v1.1.1:
- Add `UserInfoService.CLIENT_CLAIM_PREFIX`
- `IUserInfoService.GetCurrentClientIdAsync()` now returns a `string` as `ClientId` to be in sync with **Dangl.Identity**
- Added `ClientCredentialsLoginAsync` to `DanglIdentityLoginHandler`

## v1.1.0
- Update to stay in sync with **Dangl.Identity**

## v1.0.0
- Initial Release