wip(auth): Get fresh token before making request

[dac09]

Starts fix for #1576

• Use fresh token for getCurrentUser
• Use fresh token for other graphql requests
• Add a way to watch for token changes from client
• Verify and test this

[github-actions]

📦 Packages for this PR can be downloaded from
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/create-redwood-app-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-api-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-api-server-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-auth-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-cli-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-core-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-dev-server-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-eslint-config-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-eslint-plugin-redwood-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-forms-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-internal-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-router-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-structure-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-testing-0.21.0-9cb74f0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1577/redwoodjs-web-0.21.0-9cb74f0.tgz

Install this PR by running yarn rw upgrade --pr 1577:0.21.0-9cb74f0

[peterp]

I'm a bit cautious of this approach, since it changes a bunch of assumptions and I'm not fully grokking the consequences of that.

Backing up a bit. I think the root cause for this problem is that we're not dynamically requesting the auth token on each request.

This is solvable in Apollo by using an http auth-link (pseudo-code):

import { AuthContext } from '@redwoodjs/auth'

const authLink = setContext((_, { headers }) => {
  // get the authentication token
  const { token } = AuthContext._currentValue

  // return the headers to the context so httpLink can read them
  return {
    headers: {
      ...headers,
      authorization: token ? `Bearer ${token}` : "",
    }
  }
});

[viperfx]

My redwood app is still pre-production, but I face this almost on a daily basis during development. Token expires and all subsequent navigation inside redwood gives a 500 status from the API. (I am using Firebase as well).

Would the above suggestion with auth-link be implemented on global level in redwood or on an auth provider level?

[peterp]

@viperfx We'll solve this for everyone.

[dac09]

Closing this, new solution on the way.