What is the 'Run As Owner' option when running a Burst?
Bryan Baca
started a topic
1 day ago
A user asked about the purpose of the 'Run As Owner' option they see when running a Burst.
A Burst is a series of dependencies. Let’s say the Burst contains a WebI document with a SharePoint delivery. When the Burst is executed, credentials for the respective BusinessObjects and SharePoint Platforms are required. When a user runs a Burst, that user's Platform credentials are utilized. The ‘Run As Owner’ option gives an Administrator user the option to run the Burst as the user who created the Burst. If an Administrator user selects 'Run As Owner' and executes the Burst, then the Platform credentials of that Administrator user will be utilized. The option is not visible for non-administrator users.
The Administrator user must understand why they would want to run a Burst as another user. The option exists largely for troubleshooting purposes. Let’s say a user reports to an administrator that their Burst is failing, but they don’t know why. The administrator starts investigating. Let’s say the administrator runs the Burst and it works for them. That might be a clue that the issue is related to the user context. The administrator checks the ‘Run As Owner’ option, runs the Burst, and discovers the Burst is failing because the Burst owner’s BusinessObjects credentials are invalid.
Bryan Baca
A user asked about the purpose of the 'Run As Owner' option they see when running a Burst.
A Burst is a series of dependencies. Let’s say the Burst contains a WebI document with a SharePoint delivery. When the Burst is executed, credentials for the respective BusinessObjects and SharePoint Platforms are required. When a user runs a Burst, that user's Platform credentials are utilized. The ‘Run As Owner’ option gives an Administrator user the option to run the Burst as the user who created the Burst. If an Administrator user selects 'Run As Owner' and executes the Burst, then the Platform credentials of that Administrator user will be utilized. The option is not visible for non-administrator users.
The Administrator user must understand why they would want to run a Burst as another user. The option exists largely for troubleshooting purposes. Let’s say a user reports to an administrator that their Burst is failing, but they don’t know why. The administrator starts investigating. Let’s say the administrator runs the Burst and it works for them. That might be a clue that the issue is related to the user context. The administrator checks the ‘Run As Owner’ option, runs the Burst, and discovers the Burst is failing because the Burst owner’s BusinessObjects credentials are invalid.