Forum Discussion
You are correct – when the pipeline executes, it executes with the permissions of the task owner even if another user triggers it. So in the dashboard, it shows the task owner rather than the user who triggers it because that’s really the user who is executing the pipeline.
A triggered task can be authorized by using a username/password or a bearer token. When the task is triggered, the method of authorization is recorded. In the case of a username/password, it would store the username. So in your example it would show user2 there.
I don’t see that detail exposed anywhere in the UI. Let me ask around or see if an enhancement should be filed.
- Ajay_Chawda7 years agoContributor
Thanks @tlikarish for response. we are looking for user2 information.
- tlikarish7 years agoEmployee
Sounds like this isn’t exposed in the UI yet. I’ll work on getting an enhancement filed for this feature.
- sanjaynayak5 years agoNew Contributor III
@tlikarish what is use of service account, it seems to be useful for authorization to call a trigger task but it is failing but task owner id and password is working as basic authorization.