Hi! Let's talk a little bit about user authentication. We'll discuss it through the context of authentication
within Artsy's ecosystem of applications, but ideally the same concepts will translate into other systems as well.
The goal here is to build an understanding of (1) what exactly authentication is, (2) how it works, and (3) how to
use artsy's specific infrastructure to delegate authentication for a new application to the existing ecosystem.
There are two primary authentication flows that we use at Artsy. We support user authentication through
OAuth to allow users to log into our applications by delegating authentication to Gravity,
our primarily application API. Alternately, we support app authentication for those cases where an application
will only be called by other applications. We don't care about user authentication in this context, there's no need
to redirect to a login screen etc - we just need to establish permissions between services. In both cases you'll be
working with JSON Web Tokens (JWTs), and the difference is how the token you're
looking at is generated.
User authentication happens at login - when the user provides their credentials to our server, our server confirms
that they are who they claim to be and then generates a cryptographically signed token that encodes a few facts
about that user.
App authentication, by contrast, all gets done in advance. We create the token manually, and share it with whatever
application we want to grant access to.
In this document we'll first develop an understanding of what OAuth is and how it works. Then we'll examine the
tokens we're using to get a better sense of what kind of information we have to work with. Finally, we'll go into
how to set up authentication for users and for applications, building on the knowledge we've established.
Read on →