In this post I’m going to take you through the steps of setting up a Neo4J instance on Digital Ocean and how to secure it with either the Authentication Extension if you are using a version of Neo4J 2.1.x and below or the out of the box functionality in 2.2.x. and above.
Out of the box the Neo4J administration console is not secured, aside from the fact it only accepts connections from localhost by default. So if you are going to release your application into the wild you will need some way to secure it, and accept connections from other machines.
Neo4J is unusual in that it offers more than one production viable configuration for integrating with software. At a glance these are limited to either Embedded or Server, and I would suspect (completely unscientifically) that the most commonly asked question about on Neo4J is “Embedded or Server?” in some variation.