Skip to main content

Hi there,

 

I have a simple question. How to change "Initiating user" for a workflow.

I am digging through the documentation without success. Do you know it from the top of your head?

 

Cheers!

 

Hi @Rob and @Mike Struening ! Thank you for your inputs.

Rob, this is it! Your advice is the right one. When I use ImpersonateLogin activity it works as I need. Everyone can execute the workflow, but the backup job itself is started by the user defined in ImpersonateLogin box. Thanks.

 

 


Hi @drPhil,

I think there is some confusion here.

 

ImpersonateExecutor will run the following commands as the person that executed the workflow.
This is useful to change the context back to the workflow executor if it as been changed before.

ImpersonateCreator, is as it sounds, the following activities will be run as the user who created the workflow.

What you need in ImpersonateLogin, this allows you to set the creadentials of the user who will run the next actions.

 

So to run a workflow as “admin” but have the workflow run a backup as “student” you would want something like this:


 

Hope this helps,

Rob

 


Tagging in @Chris Sunderland .  I’m likely missing the obvious!


Hi @Mike Struening, it is really strange. My Insert Variable option is grey.

 

 

 


@drPhil , you should see the options on the Input tab/


Hi @Mike Struening! Thanks for the input.

Now, I am struggling with adding my variable into ImpersonateExecutor activity. Let’s say, the user ’student’ should be the executer of the simple backup job activity. It means, in Commvault it should be written that job was started by  ’student’ even if other user executes the workflow.

 

However, where to define this variable? I tried everything and changed all values with the name in description.

 

 

So, how to force Commvault to start the backup job by the desired user? Where to define this variable?

 

 


Hi @drPhil , hope all is well!

By default, the WF will run as ‘you’, the person running the WF itself.

However, you can change the executor by using the ImpersonateExecutor activity:

https://documentation.commvault.com/11.24/expert/49663_built_in_activities_for_workflows.html

This other page has more security options that might come up for you:

https://documentation.commvault.com/11.24/essential/134220_workflow_security.html

Let me know if that helps!


Reply