Error when token revoked
Would expect to treat a revoked token like a new user and ask to be authorized, instead fails with error message. In ualbertalib/hydranorth based on projecthydra/sufia with browse-everything configured, visiting the Upload Cloud Provider Google Drive authorize the app, then editing your Google Account Permissions to revoke access to the app will result in the failure.

One problem is that the controller sets the grant token in the session and the lib adapters are not expected to have access to the session. So when the 401 happens inside the adapter, its client-specific code cannot clear out the session. Essentially, we need a different approach.
This was fixed with the Box driver in 43ed399d2170132a57261f4261a31e6aec699574