Artsy.github.io Website Review

EVERYTHING YOU EVER WANTED TO KNOW ABOUT AUTHENTICATION AT ARTSY (BUT DIDN'T KNOW HOW TO ASK) 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 allow users to log into our applications by delegating authentication to Gravity, our primarily application API. Alternately, we support 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 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 In this docu*ent 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 Volt is the internal app name of Artsy CMS, and our partners use it to manage their inventory and presence on artsy.net. It's a Rails-based model, view, and feature specs. As of Jun. 2018, Volt had 3751 specs and 495 of them were run with Ja*aScript enabled. It took about 16 Capybara-webkit was introduced from the very beginning of Volt for testing Ja*aScript-enabled specs via headless WebKit browser. It's Hey everyone! I'm Justin, a senior engineer here at Artsy. I've been here for about 6 months and I'm a bit overdue on my first blog post.