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
For scheduled jobs, there needs to be a secure mechanism for Job Scheduler to issue new access tokens on behalf of the user associated with a job to provide to a job runner. In the current plugin architecture, plugins persist the user's roles roles at time of creation in the job details index associated with the plugin and then inject them into the ThreadContext when the job executes to evaluate privileges. For extensions, this model is being changed in favor of stored user info associated with a job in a single secure index.
Job Scheduler can use then identity system to request a new access token on behalf of a user associated with a scheduled job stored in the scheduled job identity index.
The text was updated successfully, but these errors were encountered:
cwperks
changed the title
Create secure mechanism for vending access tokens to user absent of the user present for job scheduler
[Extensions] Create secure mechanism for vending access tokens to user absent of the user present for job scheduler
Mar 31, 2023
cwperks
changed the title
[Extensions] Create secure mechanism for vending access tokens to user absent of the user present for job scheduler
[Extensions] Vend new access token provided a refresh token
Mar 31, 2023
stephen-crawford
added
triaged
Issues labeled as 'Triaged' have been reviewed and are deemed actionable.
and removed
untriaged
Require the attention of the repository maintainers and may need to be prioritized
labels
Apr 3, 2023
cwperks
changed the title
[Extensions] Vend new access token provided a refresh token
[Extensions] Issue access token on behalf of user stored in scheduled job identity index
May 16, 2023
For scheduled jobs, there needs to be a secure mechanism for Job Scheduler to issue new access tokens on behalf of the user associated with a job to provide to a job runner. In the current plugin architecture, plugins persist the user's roles roles at time of creation in the job details index associated with the plugin and then inject them into the ThreadContext when the job executes to evaluate privileges. For extensions, this model is being changed in favor of stored user info associated with a job in a single secure index.
Job Scheduler can use then identity system to request a new access token on behalf of a user associated with a scheduled job stored in the scheduled job identity index.
The text was updated successfully, but these errors were encountered: