Add more fields to the CI_JOB_JWT
Problem
As a customers i cant decide on our 3rd party system if a pipeline was started by a real user which had 2FA enabled.
Solution
To decide on a 3rd party system if a pipeline was triggered by a human, an other job, or api it would be grade to have the CI_PIPELINE_SOURCE attribute also in the jwt-token.
Additional to that it would be great when the pipeline was triggered via web if the user was 2FA authorized.
Edited by Marco Obermeyer