Releases: wultra/powerauth-push-server
Release 0.17.1
This issue fixes problem with DNS resolving behind proxy that was introduced in 0.11.x versions of Pushy library. See jchambers/pushy#560 for details.
Release 0.17.0
Hooray! This is the first version of the push server we are happy to share without the Beta
flag!
The push server has newly support for sending batch campaigns. It also handles potential APNS / FCM states much more reliably.
To update from 0.16.0, please update your database using following script.
Release 0.16.0 - First Beta
We updated model classes of the RESTful API to be more consistent with the rest of our applications. We also updated libraries.
Client library is already present on Maven Central.
<dependency>
<groupId>io.getlime.security</groupId>
<artifactId>powerauth-push-client</artifactId>
<version>0.16.0</version>
</dependency>
Release 0.15.1-alpha
Bugfix and maintenance release.
- Update libraries
- Fix minor issues with code clarity
Release 0.15.0-alpha
This update includes following enhancements:
- Token based authentication for APNs (dropped support for certificates).
- Possibility to configure proxy for APNs and FCM.
- Minor bugfixes.
Release 0.14.0-alpha
Release 0.14.0 with updated PA2.0 libraries.
Release 0.13.3-alpha
Release 0.13.2 with updated PA2.0 libraries.
Release 0.13.2-alpha
Release 0.13.2 with updated PA2.0 libraries.
Release 0.13.1-alpha (bugfix)
This release fixes issue with sequence identifiers being too long for Oracle Database.
Release 0.13.0-alpha
Alpha version of the PowerAuth 2.0 Push Server. Works with PowerAuth 2.0 Server v0.13.0.
Supports:
- Device registration process
- Registered device personalization process
- Device removal process
- Device activation status update process
- Sending single or batch messages to APNs and FCM service
- Simple PA2.0 Push Server Admin interface
Note: This version is supposed to serve as a sneak peek of the push server, use with caution in production!