AngularJS, Websockets, REST APIs for mobile apps, one-time links for emails — what’s the topmost complexity all those things share in common?
It’s authentication. Authentication typically means sessions, and sessions are simply ubiquitous state for our stateless-by-design web.
What's even worse, that state requires all the parts of your webapp to share some dynamically-changing knowledge concerning who is authorized to do what, which mobile apps were authorized to have an access and so on.
Json Web Tokens. That’s how we will be able to detach our authorization logic from everything else.
- They’re simple, both to issue, to store and to check.
- They’re URL-safe.
- They’re cryptographically safe.
- They’re stateless. (One can easily add some state on top of them if required.)
So my proposal is simple. Let’s implement the JWT-issuing server with RESTful API (I’ve already have a prototype, it’s called AuthStralia). Add some management tool on top of that (should be probably called AuthRica). And then go absolutely wild implementing JWT-validating plugins for all the possible frameworks and environments we will be able to think of. (The only appropriate name I’ve managed to invent here so far is AuthEns, so bring your atlas with you, if possible.)
And yes, AuthStralia prototype is written in Elixir lang. So if pure functional homoiconic languages with purely hygienic macro sistems are your kind of poison — you’re welcome to join just for that reason.
Looking for mad skills in:
rest functionalprogramming api authentication web elixir-lang
This project is part of:
Hack Week 11
Hackweek 18 Update
What Has Been Done ...
cosmic-river aims distributed E...
There is around in the cloju...
I will not have the time for bootstrapping this...