You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, unfortunately when using the endpoints on runtime, we get expired tokens after a while, causing our application to crash. We proceeded by using SSG for most parts of website and that works like a charm. Of course it's a requirement for some features to be able to fetch resources on the go, has anyone had any problems with this?
Are there any reported issues on token refreshing not working? Is this desired behavior?
Additional context
next-drupal 1.6.0
next 14.2.2
The text was updated successfully, but these errors were encountered:
I've also experienced this expiration token issue, causing drupal to return "Unauthorized" access for various resource calls. It think it might be related to the Next js 14 caching system, however I haven't seem able to pinpoint the problem and fix it.
Package
next-drupal (NPM package)
Ask the question
Hi all,
We're using next-drupal 1.6.0 in our next 14.2.2 project. Our JSON:API uses oauth for authentication. This is how we initialise our DrupalClient:
Now, unfortunately when using the endpoints on runtime, we get expired tokens after a while, causing our application to crash. We proceeded by using SSG for most parts of website and that works like a charm. Of course it's a requirement for some features to be able to fetch resources on the go, has anyone had any problems with this?
Are there any reported issues on token refreshing not working? Is this desired behavior?
Additional context
next-drupal 1.6.0
next 14.2.2
The text was updated successfully, but these errors were encountered: