Changelog
All notable changes to Dangl.Identity.Client are documented here.
v3.0.0:
- Update to Dangl.Identity v3.0.0 and to .NET Core 3.1
 - The OpenID Connect extensions now check the 
access_tokenexpiry and refresh the token if necessary. Additionally, locked out or deleted users are now also removed from client applications - When using the OpenID Connect extensions, it internally now calls 
AddIdentityCoreinstead ofAddIdentityand adds some required services. This might break client applications that rely on services now no longer included. Consumers should manually add these to the dependency injection configuration - The 
AddMvcWithDanglIdentityextension was renamed toAddControllersWithDanglIdentityand the internal call toAddMvcwas replaced withAddControllers. If required, consumers should manually callAddMvcin their apps - The Angular library was updated to Angular v9.1.9
 
v2.6.0:
- Added 
UserInfoandAccessTokenExtensionsin Dangl.Identity.Client 
v2.5.2:
- Added checks for the 
UserInfoServicein the Dangl.Identity.Client.MVC package to give meaningful error messages in cases of invalid configuration 
v2.5.1:
- Dropped dependency 
IdentityServer4.AccessTokenValidation 
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
 
v2.4.3:
- Add 
RequiredJwtRolesandRequiredJwtClaimstoDanglIdentityServerConfigurationto configure required claims and / or roles when using Jwt authentication 
v2.4.2:
- When 
UseDanglIdentityJwtAuthenticationis 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 
Idfor current user in Angular clientAuthenticationMessenger 
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 
UseDanglIdentityJwtAuthenticationin the configuration for Dangl.Identity totrueand ensure thatapp.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 
HttpMessageHandlerconstructor argument fromUserInformationTransmissionHttpHandlerto be better composable withHttpClientFactory - Add overload to 
UserInformationTransmissionHttpHandlerthat allows to supplyIHttpContextAccessorto be able to resolve dependencies on the fly from theRequestServices 
v2.0.3:
- Switch to 
HttpClientFactory - Introduced 
DanglIdentityHttpClientAccessorto abstract accessingHttpClientin 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.OAuthtoDangl.Identity.Client.Mvc 
v1.2.2:
- Fix deserialization error of Jwt 
Bearertokens to no longer throw exceptions on invalid input in Dangl.Identity.Client.Mvc 
v1.2.1:
Dangl.Identity.Clientis now public
v1.2.0:
- Add support for client-side integration of OpenID with Dangl.Identity as OpenID provider
 - Add 
UserInformationTransmissionHttpHandlerto share user information for requests contexts across different services IUserServicewill 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 astringasClientIdto be in sync with Dangl.Identity- Added 
ClientCredentialsLoginAsynctoDanglIdentityLoginHandler 
v1.1.0
- Update to stay in sync with Dangl.Identity
 
v1.0.0
- Initial Release