Finished my writeup on how Keratin AuthN uses and manages keys (so you don't have to). It's a story of building a better system by removing configuration. https://t.co/SPKpUK5ziN
@stravid Planning to write an article on this soon! The short of it is: AuthN gives the user a bearer token (JWT) that can be verified cryptographically by anything capable of fetching AuthN's current public key. When that key is cached, network chatter is minimal.
Why an authentication microservice? In-app libraries mix sensitive auth code and data into your complex and high-churn app. Any unrelated vulnerability you introduce can compromise accounts.
AuthN handles all of your users' account passwords (signup, reset, expire, etc.), administration (un/lock, archive, etc), and sessions (revokable!). You connect the AuthN account to an extended user profile in your app.