Releases: jembi/openhim-core-js
v5.4.0
Additional authentication mechanism for router requests
https://github.com/jembi/openhim-core-js/blob/master/config/config.md
- JWT authentication - Enable and configure the JWT settings within the OpenHIM config
- Custom Token authentication - Configure the use of custom token within the OpenHIM config. Custom tokens are configured via the specific channel
v5.2.6
Supported LTS versions of nodejs
Unsupported Nodejs 8 (Carbon) has been dropped
New Nodejs 12 (Erbium) is now officially supported and the preferred version of nodejs to run. Docker images have been updated to reflect this version of Nodejs to use
Improvements
Fixed Tests for Nodejs 12!!! 🎊 🎊
v5.3.0-alpha.2
2nd Alpha Version 5.3.0
Re-added Features
URL rewriting
Fixed Polling Channel Functionality
Improvements
Streaming Router can aggregate response body
Fixed Tests!!! 🎊 🎊
Dependency Updates
Mongoose
v5.2.5
Version 5.2.5 release
Fixed some bugs 🐛 🪲
- Fixed issue with pulling data into daily and weekly transaction reports
- Fixed npm scripts for running only unit or only integration tests
Updated Dependencies
- babel v6 [deprecated] -> babel v7
- nyc v13 -> v14
Improvements
- More useful logging relating to email configuration
- Changed links in daily and weekly reports to direct users to more relevant places on the console
- Changed the default OpenHIM instance config url to
localhost
v5.2.4
v5.2.3
v5.2.2
Version 5.2.2 release
This version has one bug fix and dependencies have been upgraded.
Bug Fixes
- Fix the polling channel's functionality which was not working in versions 5.x.x
Upgrades
- Upgrading of dependencies to latest versions. This ensures that no vulnerabilities exist within the codebase
v5.3.0-alpha.1
The routing refactoring changes made various changes to how the routing engine works within the OpenHIM. Previously, all payload messages were kept in memory while routing the transaction through to its destinations. While for small transactions this is fine, when bigger transactions are processed the OpenHIM can run out of memory and cause performance issues.
The OpenHIM also had to wait for the entire message to be read into memory before continuing the routing process, and the same applies for the response. They would need to be processed completely before responding to the client.
To combat these issues, we are not reading the entire incoming/outgoing payload into memory, but instead streaming it directly into MongoDB GridFS. This also allows us to remove the body truncate limit for storing payloads as the MongoDB limit of 16mb no longer applies.
Note: Some features have been temporarily dropped while developing this refactoring changes and will be coming back in in future, proved there is still a need for them.
