Adds organizations to JWT outputs

Add in organizations

New code-base and system

Major additions included a reworking of how custom-data works and user organization. Added an "Organization" node that a user belongs under to allow for natural groupings of users together.

Also moved to a primarily Neo4j graph for the database. The implementation includes an interface to make this system extensible and useable in other database systems as well. This version only ships with Neo4j but could probably be implemented in an SQL database as well.

In-memory cache for failed auth attempts

Provide an in-memory cache to prevent excessive authentication attempts. In general, clients (for example, the eContext API) will send a request to the Auth API each time they attempt to authenticate a user. Once a user is authenticated, a session is created, and the Auth API no longer needs to be a part of the process. When authentication in the client fails, a request is sent to the Auth API to authenticate. So, if someone runs a script and uses the wrong credentials, and attempts to classify 1,000,000 tweets, each call to the eContext API will also create a call to the Auth API, and all of the included hashing and database hits. An in-memory cache of failed attempts will allow us to bypass hashing and database when the same credentials are continually passed through and failing. Eventually, we'll also be able to automatically block based on IP address, if provided.

Adding in JWT

1.0.3

fixed when there is no secret auth fails

First production release

First production release now includes init.d scripts to start/stop the auth engine and various bug fixes from 1.0.0

Initial release

A user authentication and management API written in Python with a RethinkDB backend.

• manages uses
• authenticates a user (simple True/False) based on provided credentials