- mesh names are now created and persisted
- mesh obtains unique name from happn, if one isnt specified
- fix for data routes, tested in 7-persisted-data
- modified test script in package.json
- moved logger out into own module happn-logger
- added deprecation warnings on use of UTILITIES global and the old logger
- fixed bug in MeshClient not configuring log in standalone case
- fixed issue with users and groups being updated, and passed directly up to the client in happn - was causing a scope issue, proved in test b9-mesh-security-updateuser-re-accessresource
- fixed issue where system components were being started after user-land components, using latest version of happn 1.1.5
- using the latest version of happn 1.2.6
- created search tests
- fixed exchange function argument padding bug/#62
- fixed logger flag in bin/happner
- silence security waring by explicitly setting secure to false
- added istanbul and coveralls for coverage tests
- MeshClient options supports host and hostname option
- prevent unhandled rejection errors when using 'login/deny' and 'login/error' events instead of promise in MeshClient
- divide api.js into multiple parts in system/shared/...
- using latest version of happn 2.1.7
- added https functionality, using happn 2.2.1
- added the web token security functionality
- fixed issue where upserted user is being passed back with the password hash
- removed global.UTILITIES
- moved responseHandlerCache onto messenger instance instead of prototype
- added exclusions functionality for secure web paths
- bumped version of happn
- added .datalayer.middleware.security.cookieDomain and .datalayer.middleware.security.cookieName configurables to control happn security token
- added default /api/client and /primus/* to webroute security exceptions
- added config version and name to
client.info
- tested payload encryption
- bumped version of happn
- first browser test passing
- updated happn version 2.4.3
- added $origin special argument
- fixed bug with updateUser
- added updateOwnUser
- allowed for connection to security data change events
- we now have the connect and disconnect events being emitted by the security component
- we now added a disconnect method to the apiClient
- we now have the connection events being emitted by the happner client 'reconnect-scheduled', 'reconnect-successful', 'connection-ended'
- updateOwnUser now checks if the password is being changed, and if so expects the previous password
- updated to use happn 2.5.4
- updated to use happn 2.5.7
- updated to use happn 2.5.8
- updated to use happn 2.5.9
- updates to the datalayer to allow for plugins (ie. mongo)
- updated to use happn 2.5.12
- crypto component fixes
- fixed issue with caching in happn, upgraded happn to version 2.5.15
- Fixed memory leak and noPublish issue in happn
- bumped happn version to v 2.5.18
- added benchmarket v 0.0.4
- bumped happn version to 2.5.21
- updated tests to use {reconnect:false} options when shutting dwn test instances of happner
- Reconnect option can be now be passed into mesh.stop() to inform remotes to reconnect (default true)