I never used but you can just give it a try, right? If it doesn't work you just revert back the change. Looking from the docs I do not think you can specify it but like I said I never used it. Changing the port to 443 could also do the trick!

Thanks for the post, @Steve F !

I’m checking with the owner of the Workflow (posted below for anyone following along).

https://cloud.commvault.com/webconsole/softwarestore/#!/136/671/19287

This is something we are looking into.  Our configuration uses a non-standard port, e.g. 12345, which was tested using a script before we started at the CommVault end.

Hi @Steve F ,

Yes, it should work by changing http:// to https:// in the workflow. 

Also, the CA certificate in .cer format needs to be copied under <CV install_path>\certificates folder on the CommServer and the command importcert executed. Post this, the workflow engine service has to be restarted.

Let us know if there are any further questions.

Thank you for your reply.  We indeed found just doing the http:// to https:// needed something else.

Our project team started down the pre-script route on Friday morning.  I’ll update if we implement secure workflows.

This works.

If anyone else is doing this you will also need to change both “form URL” as it creates the URL used by “Take Backup” as “Take Backup” doesn’t have ‘http://’ before the ‘xpath’ variable.

Our initial changes were done via the XML view with debugging in the Graph view.