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
When aggregator is managing a "large" job (e.g. split across multiple backends) it has to be able to act on behalf of the user "in the background" (outside of the context of a user API request).
Necessary access tokens might not be available or expire too quickly.
Possible solutions:
User also shares refresh token in addition to access token. This doesn't seem to fall in "best practices" category security-wise at first sight.
A new mechanism for longer term machine-to-machine authentication (e.g. someting like API tokens or SSH pubkey auth)
...?
The text was updated successfully, but these errors were encountered:
When aggregator is managing a "large" job (e.g. split across multiple backends) it has to be able to act on behalf of the user "in the background" (outside of the context of a user API request).
Necessary access tokens might not be available or expire too quickly.
Possible solutions:
The text was updated successfully, but these errors were encountered: