Release 1.6.3

This release contains the following improvements and bugfixes:

• Improve performance of deleting values in table pa_unique_values.

Release 1.7.0

This release contains the following improvements and bugfixes:

• Integration of FIDO2 support into PowerAuth server compatible with a variety of software and hardware authenticators using WebAuthN protocol.
• Add support for OpenTelemetry Traceparent HTTP Header.
• User-Agent of the device approving/rejecting the operation is parsed as a Device object in callbacks and Operation detail responses.
• Dependency updates.

Second snapshot release of FIDO2 support (v2)

Second snapshot including support of FIDO2 protocol in PowerAuth (v2). Do not deploy to production, the functionality will be included in the 1.7.0 release.

Includes: https://github.com/wultra/powerauth-server/releases/tag/fido2-snapshot-20240319

Additional fix: #1417

Second snapshot release of FIDO2 support

Second snapshot including support of FIDO2 protocol in PowerAuth. Do not deploy to production, the functionality will be included in the 1.7.0 release.

Migration notes since first snapshot PoC for FIDO2 support:

1. Database migration:

• datatype of extras column in table pa_activation changed to varchar(4000)
• added tables pa_application_config and pa_fido2_authenticator
• migration guide and scripts are available in https://github.com/wultra/powerauth-server/blob/develop/docs/PowerAuth-Server-1.7.0.md

2. Updated REST API parameters:

• parameter credentialId is used consistently instead of id or externalId (in AuthenticatorDetail, AuthenticatorParameters, AssertionVerificationRequest, RegistrationResponse)
• parameter operationType changed to templateName in AssertionChallengeRequest, added optional parameter userId to personalize the request
• added parameter allowCredentials in AssertionChallengeResponse and related AllowCredentials type
• update model classes are reflected in OpenDoc: http://[host]:[port]/powerauth-java-server/swagger-ui/index.html

3. Updated signature types:

• by default all hardware authenticators use the POSSESSION signature type except Wultra hardware authenticator which uses POSSESSION_KNOWLEDGE signature type
• signature types can be configured for different authenticators in table pa_fido2_authenticator

4. Supported authenticator attestations:

• added Basic Attestation using certificates next to existing Self Attestation

5. Added configuration of FIDO2 functionality:

• it is possible to restrict allowed attestation formats using configuration key fido2_attestation_fmt_allowed in table pa_application_config as JSON array of strings, e.g. [ "packed" ]
• it is possible to restrict authenticator AAGUIDs using configuration key fido2_aaguids_allowed in table pa_application_config as JSON array of strings, e.g. [ "5ad235f4-f1f3-4803-966f-1a1950e0f155", "e9b3c0e3-1f91-4d7a-aed2-8d651851866b" ]
• it is possible to configure root CA certificates for Basic Attestation using configuration key fido2_root_ca_certs in table pa_application_config as JSON array with certificates in PEM format
• new configuration property powerauth.service.scheduled.job.fido2AuthenticatorCacheEviction to set eviction period of internal pa_fido2_authenticator cache

6. Bugfix: parameter externalId in AssertionChallengeRequest is no longer ignored
7. New validations:

• multiple registations of same credentialId no longer allowed
• persistance and checking of assertion verification counter
• protocol checked in existing PowerAuth services
• AAGUID and attestation formats are checked in case configured

8. Added logging and auditing for FIDO2 functionality, updated extras for activations and additionalData for operations

Release 1.6.2

This release contains the following improvements and bugfixes:

• Fixed Liquibase for MSSQL.

Release 1.4.4

This release contains the following improvements and bugfixes:

• Able to expose metrics for Prometheus, if enabled.

Release 1.6.1

This release contains the following improvements and bugfixes:

• Fixed SQL error for Oracle.
• Dependency updates.

PoC for FIDO2 support

Initial snapshot for PoC support of FIDO2 protocol in PowerAuth. Do not deploy to production, this release is for PoC integration purposes only.

Release 1.6.0

This release contains the following improvements and bugfixes:

• Added a non-personalized operation for the QR code login feature.
  • It is possible to create an operation with null userId value and claim it during operation retrieval.
• Allow scoping operation to a single activation ID.
• REST API changes:
  • A new endpoint to update the activation name.
  • Improved operation list (paging and filtering).
  • Enabled filtering of activation list for user by status.
  • The default size of the activation list for the user is 500.
• WAR is executable as a Spring Boot application.
• Able to expose metrics for Prometheus, if enabled.
• Memory leak in CallbackUrlBehavior for RestClient instances
• Dependency updates.

Release 1.5.3

This release contains the following improvements and bugfixes:

• Memory leak in CallbackUrlBehavior for RestClient instances.