• Added IP banning middleware; currently no way to set it
• Kick newly banned accounts
• Added database port number to configuration
• Dependency updates

Full Changelog: v1.7.0...v1.8.7

Bumping every MERN-template component version number, because it's a new year.

This is a security update.

I've replaced POST_VALIDATION_HOOK with POST_VALIDATION_HOOK_ARRAY , which can take a JSON array of hooks to send a GET message to. In addition, the resulting GET message now has a JWT authentication header, to guarantee where the message is coming from.

The old hook will stop working, and the new hook needs to be validated in your own code - so the security bug wasn't in this service, rather it was in the receiving code.

Sorry for the inconvenience.

Password recovery should now function properly.

There are also SQL files under sql/ for migrating from older versions to newer versions.

I've been working on a private fork of the MERN-template to produce a game called Egg Trainer (which you can see here), and I've imported a bunch of improvements from that private fork into this project and it's services. So there's no major changes in how the template works, but I have updated a lot of the libraries used in it.

Edit: A minor upgrade problem from 1.3.0 to 1.3.1 - you must run the following command in the auth server database:

 ALTER TABLE `accounts` CHANGE `id` `index` INT( 11 ) NOT NULL AUTO_INCREMENT;

Yay!

I'm rapidly implementing each microservice as they're needed. In this case, I've created an auth server to handle the accounts and sessions of the MERN-template. This release will be pushed to docker, but there is already a live demo available at:

dev-auth.eggtrainer.com

This will remain up and act as my dummy build when I continue on the core game server. REST requests for it can be found in rest/dev-auth-requests.rest

It should be noted that I didn't include a front-end this time; I'm going to have to do a lot of reworking in the game client to implement the features here, but I'm not scared. Bring it on!