🛹

If you deployed before 2022

A breaking change was introduced in 2022. Starting from this announcement, you would not need to generate your own authentication tokens such as client_id, client_secret, etc.
You can either start from scratch (which is painstakingly simple) - 👒Getting started, or migrate to this latest version with a new OAuth process.

Migrating from an old project

  • You need to first create a Redis instance, and define the URL of the instance in the environment variable REDIS_URL in Vercel.
    • Likewise, you can still use Upstash for this, same as above.
  • You need to revert some fields of your customised config/api.json back, where specifically the clientId and obfuscatedClientSecret should exactly match:
    • {
        "clientId": "d87bcc39-1750-4ca0-ad54-f8d0efbb2735",
        "obfuscatedClientSecret": "U2FsdGVkX1830zo3/pFDqaBCVBb37iLw3WnBDWGF9GIB2f4apzv0roemp8Y+iIxI3Ih5ecyukqELQEGzZlYiWg==",
      }
  • You also need to define userPrincipalName inside config/site.json, which is used to verify your identity when doing OAuth. It is usually your Microsoft email address.
  • You can safely delete old environment variables such as your own CLIENT_SECRETACCESS_TOKEN, and REFRESH_TOKEN.