Splunk® SOAR (On-premises)

Install and Upgrade Splunk SOAR (On-premises)

As of version 6.4.0, the visual editor for classic playbooks is no longer part of Splunk SOAR. Before upgrading, convert your classic playbooks to modern mode. Your classic playbooks will continue to run and you can view and edit them in the SOAR Python code editor.
For details, see:
This documentation does not apply to the most recent version of Splunk® SOAR (On-premises). For documentation on the most recent version, go to the latest release.

Convert a privileged deployment to an unprivileged deployment

Converting a privileged deployment to an unprivileged deployment can only be done when moving from Splunk Phantom 4.10.7 to Splunk SOAR (On-premises) 5.0.1, or once your deployment has been fully upgraded to Splunk SOAR (On-premises) 5.3.3 or higher.

Converting a privileged Splunk Phantom instance to an unprivileged instance cannot be undone. Make sure you wish to convert before running the upgrade. Attempting to convert a deployment at any other point than those listed above can damage your Splunk SOAR (On-premises) deployment.

Last modified on 02 August, 2022
repositories and signing keys packages   Upgrade a single instance

This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0, 5.2.1, 5.3.1, 5.3.2


Please expect delayed responses to documentation feedback while the team migrates content to a new system. We value your input and thank you for your patience as we work to provide you with an improved content experience!

Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters