Skip to content

Releases: ActiveLogin/ActiveLogin.Authentication

v11.1.3

18 Dec 13:48
9a09daf

Choose a tag to compare

Bugfixes

Documentation

  • Remove entries in the table of contents pointing to missing sections. by @Arthacus in PR 513

New Contributors

Full Changelog: v.11.1.2...v.11.1.3

v11.1.2

21 Nov 07:37
06f5e4d

Choose a tag to compare

Bugfixes

  • #508 Resolved an issue in the TypeScript code where a failure during the call to the internal checkStatus endpoint (e.g., due to a network error) could trigger a duplicate retry. If the first retry completed after the BankID order had already been finalized, the second retry would fail with HTTP 400 and an InvalidParameters: No such order error, since the BankID API does not allow additional calls to the collect endpoint once a status of complete or failed has been returned.
    by @elinohlsson in PR 528

Full Changelog: v.11.1.1...v.11.1.2

v11.1.1

14 Oct 09:23
1ca46e4

Choose a tag to compare

Bugfixes

  • #516 uiOptions are now stored in a cookie rather than appended to the ReturnURL. This change prevents issues caused by exceeding the 512-character limit for the ReturnUrl parameter in Auth, Sign, and Payment requests. by @Zonnex, @elinohlsson in PR 517, PR 521.
  • #520 When the ReturnUrl is sent through an Auth, Sign, or Payment request to BankID, setting it to an empty string results in a 400 Bad Request. Therefore, String.Empty will no longer be used as the default value for manual navigation back to the originating application. Instead, the default value will be set to null, which will close the security application without redirecting back. by @Zonnex in PR 519

Full Changelog: v11.1.0...v.11.1.1

v11.1.0

19 Sep 12:12
3b342c2

Choose a tag to compare

Features

  • #479 #455: Send the return URL to BankID as part of the auth/sign/payment request for BankID on the same device. This is the new recommended approach from BankID, replacing the previous method of including it as a query parameter in the autolaunch URL. Active Login currently sets it both ways; if both are provided, BankID will use the URL from the auth/sign/payment request. Custom implementations of IBankIdLauncher can be updated to use the new BankIdLaunchInfo constructor to provide the return URL.
    by @Zonnex in PR #499
  • #468: Adds an extension method for configuring client certificate, allowing a service provider to be passed in.
    by @Zonnex in PR #502

Bugfixes & Improvements

  • #504: Clarified documentation about cookies, data protection, and the need to configure a persisted key store in some scenarios.
    by @elinohlsson in PR #510
  • #508 #498: Fixes an issue where the client could continue polling BankID for status even after a transaction had already been completed. This caused a pattern where a collect call would be complete, but subsequent scheduled status checks would still run and fail multiple times, resulting in the user seeing a generic error message.
    by @elinohlsson in PR #511

Full Changelog: v11.0.0...v11.1.0

v11.1.0 RC 1

12 Sep 12:26
7d277d0

Choose a tag to compare

v11.1.0 RC 1 Pre-release
Pre-release

Features

  • #479 #455: Send the return URL to BankID as part of the auth/sign/payment request for BankID on the same device. This is the new recommended approach from BankID, replacing the previous method of including it as a query parameter in the autolaunch URL. Active Login currently sets it both ways; if both are provided, BankID will use the URL from the auth/sign/payment request. Custom implementations of IBankIdLauncher can be updated to use the new BankIdLaunchInfo constructor to provide the return URL.
    by @Zonnex in PR #499
  • #468: Adds an extension method for configuring client certificate, allowing a service provider to be passed in.
    by @Zonnex in PR #502

Bugfixes & Improvements

  • #504: Clarified documentation about cookies, data protection, and the need to configure a persisted key store in some scenarios.
    by @elinohlsson in PR #510
  • #508 #498: Fixes an issue where the client could continue polling BankID for status even after a transaction had already been completed. This caused a pattern where a collect call would be complete, but subsequent scheduled status checks would still run and fail multiple times, resulting in the user seeing a generic error message.
    by @elinohlsson in PR #511

Full Changelog: v11.0.0...v11.1.0-rc-1

v11.0.0

15 Aug 09:04
7d154b3

Choose a tag to compare

What's Changed

Full Changelog: v10.1.0...v11.0.0

v11.0.0 RC 2

25 Apr 14:12
0929185

Choose a tag to compare

v11.0.0 RC 2 Pre-release
Pre-release

What's Changed

  • Revert to .Net 8 since certificate issues in .Net 9 is not yet resolved. by @elinohlsson in #501
  • Implement support for BankID:s Payment API by @elinohlsson in #503

Full Changelog: v11.0.0-rc-1...v11.0.0-rc2

v11.0.0 RC 1

07 Mar 12:46
419c660

Choose a tag to compare

v11.0.0 RC 1 Pre-release
Pre-release

What's Changed

  • Target .NET 9 @Zonnex in #494 #484
  • Add support for requirement Card Reader to Auth and Sign request. by @Zonnex in #495 #389
  • Remove support for blocking transactions based on risk level, since no longer supported by BankID. Use return risk instead and handle risk level in your application by @elinohlsson in #496 #485

Breaking Changes

This a major release, with some breaking changes. Most of them should go unnoticed for the majority of installations.

The most important ones are listed in the file BREAKINGCHANGES.md in the root of the repo.

Full Changelog: v10.1.0...v11.0.0

v10.1.0

23 Jan 09:36
1ccbbe2

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v10.0.1...v10.1.0

v10.1.0 RC 1

21 Jan 08:56
e023717

Choose a tag to compare

v10.1.0 RC 1 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v10.0.1...v10.1.0-rc-1