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
In the IETF 121 OAuth meetings, I presented on the topic of how to support "batch processing" transactions within the Transaction Token spec (Issue 111). It was recommended to bring this topic to WIMSE as regardless of whether the batch processing is more workload centric or user centric, at lot of the same challenges exist.
Maybe not a "batch process" but a long running user process is "Delete my account". In most systems coordinating the deletion of the user's data across all systems can take some time and have different system SLAs.
As a long-running workload kicks off... there is one authorization regarding whether the effort itself is authorized. Additionally, as the process continues, there may be needs to obtain transaction tokens for specific calls.
The text was updated successfully, but these errors were encountered:
In the IETF 121 OAuth meetings, I presented on the topic of how to support "batch processing" transactions within the Transaction Token spec (Issue 111). It was recommended to bring this topic to WIMSE as regardless of whether the batch processing is more workload centric or user centric, at lot of the same challenges exist.
Maybe not a "batch process" but a long running user process is "Delete my account". In most systems coordinating the deletion of the user's data across all systems can take some time and have different system SLAs.
As a long-running workload kicks off... there is one authorization regarding whether the effort itself is authorized. Additionally, as the process continues, there may be needs to obtain transaction tokens for specific calls.
The text was updated successfully, but these errors were encountered: