Thanks, that's what I was thinking. Unless I've missed something (I only speed read it) you would need to pass database login credentials when calling a database select, update etc. Would that not mean that you HAVE to store the credentials client side? I'm sure I've missed something.
Oh, OK. So this is more for back end node.js stuff than as a practical solution for calling a Neo4j database from a web browser session (unless the database credentials are specifically entered via a form as you say). Really great project, thank you guys very much for all your hard work 🙂
Note: you could implement a custom authenticator/authorizer which accepts OAuth tokens and maps those to the appropriate Neo4j user/privileges. Then the JavaScript driver can send the OAuth tokens as the "passwords". We do this for the Neo4j Sandbox.
Hi Ryan, I don't know Java and was wondering if there is any pre-built plugin I can use? I am building a JS app and would like to authenticate the user with a token every time I run a session which I would receive once the user logs in to the app. On login the user credentials would be send to Neo4j and the browser would receive and store a token which I would then use in subsequent sessions (currently I establish and close a session with every query). Is this the right approach? Thank you
To confirm, you have some server-side code? What's your server-side written in? NodeJS?
Typically the server-side code would authenticate and authorize the user and then perform the database requests on behalf of the user -- rather than connecting the frontend JS directly to the DB.
