drush queue:run atmosphere_update
[error] Failed to update node 9334: Token request failed: Invalid client ID "http://default/atmosphere/client-metadata"
[error] Failed to update node 9334: Token request failed: Invalid client ID "http://default/atmosphere/client-metadata"
...
This was on an update. Client metadata shows correctly at https://dev.paullieberman.net/atmosphere/client-metadata. Once again it went into an endless loop of retrying before I killed it.
I then went back into the configuration, disconnected, and logged in again to my PDS. I then tried the update again and it succeeded.
drush queue:run atmosphere_update
[success] Processed 1 items from the atmosphere_update queue in 0.73 sec.
I do not believe Oauth connections are robust enough for background processes. I believe handle/app password is better for this purpose. Oauth is much better for interactive sessions on a third party app. Since this is running on my own Drupal site, connecting to my own PDS, I don't think there are any security concerns with handle/app password authentication.
This was on an update. Client metadata shows correctly at https://dev.paullieberman.net/atmosphere/client-metadata. Once again it went into an endless loop of retrying before I killed it.
I then went back into the configuration, disconnected, and logged in again to my PDS. I then tried the update again and it succeeded.
I do not believe Oauth connections are robust enough for background processes. I believe handle/app password is better for this purpose. Oauth is much better for interactive sessions on a third party app. Since this is running on my own Drupal site, connecting to my own PDS, I don't think there are any security concerns with handle/app password authentication.