Releases: wultra/powerauth-restful-integration
Releases · wultra/powerauth-restful-integration
Release 1.1.0
This release contains following improvements and bugfixes:
- Dynamic resource ID resolution in PowerAuth annotations.
- Proper initialization of custom attribute map.
- Dependency updates.
Release 0.24.1
Release 1.0.0
This release contains following improvements and bugfixes:
- REST client migrated to the
rest-client-base
project. - Added context to the activation provider interface.
- Support for activation flags and application roles.
- Improved logging.
- Dependency updates.
Release 0.24.0
This release contains following improvements and bugfixes:
- Optional OTP code verification during activation.
- Device platform and model information is stored during activation.
- Recovery codes can be revoked on activation removal.
- Dependency updates.
Release 0.22.4
This release contains following improvements and bugfixes:
- Improved recovery code revocation during activation removal.
- Dependency upgrade to PowerAuth Server version 0.22.2.
Release 0.23.1
- Added a cleanup callback after activation is removed.
- Added default implementation to the activation provider interface.
Release 0.22.3
- Added a cleanup callback after activation is removed.
- Added default implementation to the activation provider interface
Release 0.23.0
This release contains following improvements and bugfixes:
- Improved information entropy in PowerAuth online signatures using BASE64 encoding.
- Improved protection of encrypted status blob against possible replay attacks.
- Improved protection of payload encrypted by our ECIES scheme.
- Improved protocol reliability by allowing the mobile client to synchronize its counter with the server.
- PowerAuth RESTful API separated from validation logic.
- Bouncy Castle library upgraded to
1.64
. - Dependency updates related to security advisories.
Release 0.22.2 - hotfix
This hotfix release provides possibility to handle PowerAuthActivationException
outside of activations:
- #199: Allow processing of PowerAuthActivationException during custom activations