Require signin for Meadow

[kdid]

• Using the app or API requires login with NU SSO:
  • Adds "Accounts" context in Meadow for user and groups related functionality
  • Adds AuthController - SSO callback finds or creates user in database and stores some user information in session
  • SetCurrentUser plug intercepts all API requests and checks for user session. Puts the current user into the Absinthe execution context
  • Adds Absinthe Middleware Authenticate which checks for the current user in the context and if found resolves the query.
  • Adds a GetCurrentUser query that returns the currently logged in user
  • Adds RequiresSignIn and CurrentUser components to the front end to guard the app

**Authorization was out of scope for this unit of work. For this PR anyone with a NetId can log in and use Meadow.

[kdid]

@adamjarling - I added skip to one JS test as I wasn't sure how best to address.

[adamjarling]

All in all I think this is really good (from the React side) and works as expected. I'd like to merge this in, then take a crack at building off this branch with the following strategy for protected routes, and globally exposing a currentUser object w/o Redux.

<Auth /> component wraps the app, similar to <RequireSignIn />, and uses/sets/reads a React Context auth/currentUser variable which can be accessed throughout the app.

[adamjarling]

What about creating a /assets/js/components/Auth directory, where we can organize Auth related components (CurrentUser, RequireSignIn) and queries? Then we could create .../Auth/auth.query.js or something and avoid exporting from individual components?

[kdid]

Yeah. I think that's a good idea. Some of that stuff didn't seem to fit anywhere so I just threw it somewhere. Let me see if BMQ and MBK have comments and I'll change at same time.

[adamjarling]

Might not need this if not a link or form submit action.

[mbklein]

Looks great except for one small comment.