Cannot remove Acquia DAM authorization if token expires, causing WSOD for all DAM functionality

Balu Ertl → made their first commit to this issue’s fork.

I feel it worth to clarify that the issue is about the Drupal user's authentication token (marked with green) and not the site's one (marked with red):

However, by following the described steps I could not reproduce the WSOD issue as expected on the 2.x branch. My testing steps were in order:

1. Install the module by Composer, then enable the parent and its Example Config sub-module by Drush
2. Configure its site-wide settings on /admin/config/media/acquiadam with valid credentials
3. Authorize Drupal user account on /user/{UID}/edit
4. Test the proper way of working by creating a media item based on an Image type of DAM asset
5. The media item should have a thumbnail and its name should be the asset title (usually a file name-like string)
6. In the users_data table of the DB find your actual user account's row. Modify its value field by replacing the alphanumeric string under the serialized acquiadam_token key to something non-sense (like 0123456789abcdef0123456789abcdef). Ensure that the complete JSON value still starts with the term “wat_…” (acronym of Widen Access Token).
7. Flush all caches.
8. Test the erroneous way of working by creating another media item (eg. by sticking with the Image type of DAM asset).
9. The media item is being created in Drupal but has no thumbnail (only a general placeholder image appears instead) and its name does not resemble any filename. (This is because no metadata was available due to the disconnection from the remote DAM system)
10. Visit Watchdog and filter for the module name. Several log messages were emitted, some of them similar to these:

    • Received a missing asset response when trying to load asset f2a9c03d-3664-477c-8013-e84504ed5adc. Was the asset deleted in Acquia DAM? DAM API client returned a 401 exception code with the following message: Client error: `GET https://api.widencollective.com/v2/assets/f2a9c03d-3664-477c-8013-e84504...` resulted in a `401 Unauthorized` response:

      {
        "error": true,
        "response_code": 401,
        "error_message": "Unauthorized",
        "stack_trace": null
      }
      

    • Failed to fetch asset ids: Client error: `GET https://api.widencollective.com/v2/assets/search?limit=100&offset=0&quer...` resulted in a `401 NOT AUTHORIZED` response.

    • Unable to register integration link for asset f2a9c03d-3664-477c-8013-e84504ed5adc. Exception message: Client error: `POST https://laser.widencollective.com/api/rest/integrationlink` resulted in a `401 Unauthorized` response:

      {
        "error":"invalid_request",
        "description":"No access token."
      }
      

11. Switching back the valid “wat_…” string in your user account's record of the DB (and flushing caches again) everything should work normal.

Update: I just realised that my testing procedure described in #9 above is unrelated to this original issue. The unauthentication link needs to be clicked on the /user/{UID}/edit page instead, and then WSOD happens indeed. Sorry for the confuse.

Automatically closed - issue fixed for 2 weeks with no activity.