I have a site that was set up successfully to a connect to a DAM instance, and the users authorized to use the DAM to place images. I needed to clone this site, and connect the clone to a new DAM instance.
Updating the DAM settings to point to the new DAM instance with a new API token was straightforward enough. Updating the user authorizations was a different story, however. When I go into a user account and click to remove the authorization (so I can then authenticate into the new DAM instance), I get a fatal error because the new instance returns a 401 error to the request.
I would suggest two fixes:
- The code that removes the DAM authorization should have some built-in error handling so that an error can be logged but the user doesn't see a WSOD
- When the DAM connection is changed centrally, it should automatically remove the authorization for all authorized users before switching the connection
I'm tempted to mark this as a major error because of the WSOD and the fact that resolving the problem once you have it is a major effort, but I recognize that users changing their DAM connection probably happens infrequently.
Active
2.0
Code
Changes in the MR allowed me to successfully unauthorize a token from the old DAM domain.