API Key based authentication

[urban-1]

These changes are fairly old and been tested for a long long time, so I think they could be merged.

The main feature is API key based authentication. Few other stuff have been changed in order to make uLogin more flexible or ease configuration (dynamic database settings and lazy log cleaning instead of cron). For more details see the ChangeLog.

NOTE: Along with the API key implementation we were experimenting with key statistics. The main goal was to be able to get usage information for each key and throttle the requests. Usage info works nicely, however, throttling is heavy and does not worth it. Back when we were profiling it, it seemed that used more than 50% CPU time which means that instead of trying to limit clients/keys we could double our capacity by not auditing access! This should be disabled by default.

Let me know if there questions

[urban-1]

Hey @pylorak

How are you? I know it has been a very long time - I know... but I am thinking of picking this up again for a project of mine. Do you still maintain this repo? If not, I am willing (given time!) to merge @icanhazpython changes in my fork and take it from there...

BTW, it seems there are few other projects for authentication, have you moved to something else? - I really like this one though. Lately I had some exposure to SAML so I can try to add this as a feature (if not there already - don't remember!)

Let me know (you should also have my personal email from old comms)

Cheers,

Andreas

[chocolatkey]

@urban-1 It would be great if you picked this back up! I always used ulogin for authentication, and was very satisfied with it, but It's slightly outdated now.