5.1 - Make Next permitted poll time available for all responses

New

• The responses, JobStatusChanged and JobStatusResponse does now always include a Next 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 time available for these as well.

5.0.4 - Upgrade User-Agent and dependencies

New

• The user agent is now posten-signature-api-client not digipost-signature-api-client. A minor change, but more correct.

A few dependency upgrades:

• Bump CompareNETObjects from 4.57.0 to 4.58.0 (#183)
• Bump NLog from 4.5.11 to 4.6.1 (#191)
• Bump Microsoft.NET.Test.Sdk from 15.9.0 to 16.0.0 (#185)

5.0.3 - Upgrade dependencies

New
A bunch of brand new dependency upgrades:

• Bump Microsoft.Extensions.Logging from 2.1.1 to 2.2.0
• Bump Microsoft.Extensions.DependencyInjection from 2.1.1 to 2.2.0
• Bump xunit from 2.3.1 to 2.4.1
• Bump CompareNETObjects from 4.3.0 to 4.57.0
• Bump Microsoft.Extensions.Logging.Debug from 2.1.1 to 2.2.0
• Bump NLog.Extensions.Logging from 1.3.0 to 1.4.0
• Bump Microsoft.Extensions.Logging.Console from 2.1.1 to 2.2.0
• Bump Microsoft.NET.Test.Sdk from 15.5.0 to 15.9.0
• Bump Microsoft.AspNet.WebApi.Client from 5.2.6 to 5.2.7
• Bump xunit.runner.visualstudio from 2.3.1 to 2.4.1

5.0.2 - NET Core 2.1 🎉

Technical

• The library was previously named signature-api-client-dotnet. To conform better with naming conventions and package structuring, the library now has several packages with the prefix Digipost.Signature.Api.Client.. If you are using the portal cases, use Digipost.Signature.Api.Client.Portal, and for direct cases, use Digipost.Signature.Api.Client.Direct
• The library is now NET Core 2.1.
• Certificate loading should now be done by file, as the previous loading by certificate thumbprint has not been tested extensively.
• Please see the documentation for more information on all the changes.

Bugfixes

No bugfixes, but please report any bugs you might find.

4.4.0 – Includes order attribute for portal jobs

Technical

• Removed strong name signing. Consumers of the library requiring a signed assembly in GAC are required to manually sign it.

Bugfixes

• The order attribute when creating portal jobs was not previously included in the XML sent to the service, as reported in #141.

4.3.0 - Includes job reference in all responses

In addition to the signature job's ID, the reference (when specified by the sender upon creation of a job) is also included in all responses from the service. This is handy for certain senders who don't want to persist the service's ID in their own system.

v4.2.0 - Adding queue support

Specifies the queue that jobs and status changes for a signature job will occur in. This is a feature aimed at organizations where it makes sense to retrieve status changes from several queues. This may be if the organization has more than one division, and each division has an application that create signature jobs through the API and want to retrieve status changes independent of the other division's actions.

To specify a queue, set Sender.PollingQueue through the constructor Sender(string, PollingQueue). Please note that the same sender must be specified when polling to retrieve status changes.

4.1.2 - Enables to send on behalf of for portal jobs

Bugfix

• Having problems sending on behalf of other for portal jobs? This was merely the result of poor craftsmanship and/or a shy property. Signer.OnBehalfOf will now be properly assigned.

4.1.1 - Adds possibility of mocking signatures

Bugfixes

• Creating a mocked Signature for portal jobs was unintentionally removed in version 4.0.0. It is now back as requested in issue #110 .🏄

4.1.0 - Exclude personal identification number in signed document

New

• Job now has the field IdentifierInSignedDocuments which specifies what will be shown in PAdES and XAdES as identifier for a signer. For a full specification of valid options, please see the API specification.