The api is designed such that every request requires an access_token . However, if a user is not logged in(or doesn't have an account) they will not have an access_token .
This creates a problem because the frontend relies on the api to fetch the website content. To get around this problem a user with a publicly known access token must be created.
On the client side if the user is not authenticated the client will use a publicly known access_token.
The api is designed such that every request requires an
access_token
. However, if a user is not logged in(or doesn't have an account) they will not have anaccess_token
.This creates a problem because the frontend relies on the api to fetch the website content. To get around this problem a user with a publicly known
access token
must be created.On the client side if the user is not authenticated the client will use a publicly known
access_token
.