Releases: digipost/signature-api-client-dotnet
Releases · digipost/signature-api-client-dotnet
7.0.3 - Upgrade dependencies
- Replace api-client-shared 4.0.0 => Digipost.Api.Client.Shared 7.0.1. Same code, new package name. This bump introduce no change in functionality. See https://github.com/digipost/api-client-shared-dotnet/releases
- Bump Microsoft.NET.Test.Sdk from 16.8.0 to 16.8.3
7.0.1 Upgrade dependencies
- Bump Microsoft.Extensions.Logging from 3.0.0 to 3.1.2
- Bump Microsoft.Extensions.Logging.Debug from 3.0.0 to 3.1.2
- Bump Microsoft.Extensions.Logging.Console from 3.0.0 to 3.1.2
- Bump Microsoft.Extensions.DependencyInjection from 3.0.0 to 3.1.2
- Bump NLog from 4.6.7 to 4.6.8
- Bump NLog.Extensions.Logging from 1.5.4 to 1.6.1
- Bump CompareNETObjects from 4.63.0 to 4.65.0
- Update Microsoft.Extensions.Configuration.UserSecrets requirement
- Improved documentation for Client Configuration.
7.0.0 - Target .Net Standard 2.0
Changed target framework to .NET Standard 2.0, instead of .NET Core. This means that the client now works with .NET Framework <= 4.6.1 and .NET Core <= 2.0 (https://docs.microsoft.com/en-us/dotnet/standard/net-standard).
6.2.0-beta - Client configuration med proxy config
Update .travis.yml (#238)
6.1.0-beta - Archive client
6.0.0 - Request new redirect URL for signing in direct flow
New:
- It was a big chance that one of the signers in a direct flow scenario would change their mind and try to sign later. As the redirect URL could only be retrieved once, this would prevent the signature job from being successfully signed by all the signers and had to be created again. We realized that this is annoying, and are now pleased to announce that a new redirect URL can be retrieved per signer for a specific job. How to do this, you ask? Just call DirectClient.RequestNewRedirectUrl. 👏
- The client library configured the TLS setting manually, which is unfortunate for some users of the client library. (#218, #217)
- Bump NLog from 4.6.3 to 4.6.7 (#215, #212, #208)
- Upgrades Travis submodule (#214)
- Bump CompareNETObjects from 4.58.0 to 4.62.0 (#201, #211)
- Bump Digipost.Signature.Api.Client.Direct from 5.0.3 to 5.1.0 (#202)
- Bump Digipost.Signature.Api.Client.Portal from 5.0.3 to 5.1.0 (#203)
- Bump Microsoft.NET.Test.Sdk from 16.0.1 to 16.2.0 (#209)
- Bump NLog.Extensions.Logging from 1.5.0 to 1.5.4 (#219 #210)
6.0.0-RC3 - Upgrade dependencies and submodule
6.0.0-RC2 - Upgrade Dependencies
New
A bunch of brand new dependency upgrades:
- Bump CompareNETObjects from 4.58.0 to 4.59.0 (#201)
- Bump Digipost.Signature.Api.Client.Direct from 5.0.3 to 5.1.0 (#202)
- Bump Digipost.Signature.Api.Client.Portal from 5.0.3 to 5.1.0 (#203)
- Bump NLog from 4.6.3 to 4.6.5 (#208)
- Bump Microsoft.NET.Test.Sdk from 16.0.1 to 16.2.0 (#209)
- Bump NLog.Extensions.Logging from 1.5.0 to 1.5.2 (#210)
6.0.0-RC1 - Request new redirect URL for signing in direct flow
New:
- It was a big chance that one of the signers in a direct flow scenario would change their mind and try to sign later. As the redirect URL could only be retrieved once, this would prevent the signature job from being successfully signed by all the signers and had to be created again. We realized that this is annoying, and are now pleased to announce that a new redirect URL can be retrieved per signer for a specific job. How to do this, you ask? Just call
DirectClient.RequestNewRedirectUrl. 👏
5.1 - Make Next permitted poll time available for all responses
New
- The responses,
JobStatusChangedandJobStatusResponsedoes now always include aNext permitted poll time, making it possible to rely on the poll time when fetching new receipts, regardless of if it failed or not. - Checks if we are blocked by the DoS-filter, and makes
Next permitted poll timeavailable for these as well.