Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Trying to enable Native REST API via CLI arguments

Ashis | Last updated: May 21, 2021 08:36AM UTC

Follow below steps make the settings under User Options - > Misc - > REST API enable "Service running" enable "Allow access with out API key" Now save with "Save Options" to save the json file. let the name of the json file be /path/abc.json Now, disable "Service running" disable "Allow access with out API key" close burp. running the BURP with CLI option as in https://portswigger.net/burp/documentation/desktop/getting-started/launching/command-line i.e., java -jar /path/to/burp.jar --config-file=/path/abc.json Expected behaviour : Burp should launch with Service running in "enabled" state and Allow access with out API key in "enabled" state. However, Observed Service running in "disabled" state and Allow access with out API key in "disabled" state. Please help wrt this.

Hannah, PortSwigger Agent | Last updated: May 21, 2021 09:59AM UTC

Hi

The REST API configuration is a user-level configuration.

Have you tried using --user-config-file instead of --config-file?

The full list of command-line arguments can be found here.

Ashis | Last updated: May 21, 2021 01:21PM UTC

Thanks, this seems to fix the issue. Any reference to check if a config type is of 'user-config' type?

Hannah, PortSwigger Agent | Last updated: May 21, 2021 01:31PM UTC

If it's under the "User options" section, that is a user-level configuration. This persists across reloads of Burp and different project files (unless otherwise specified). A project-level configuration needs to be set each time you open a fresh project. In the JSON configuration, you can tell which is which, as each will start with either of the following: - "project_options" - "user_options"

Ashis | Last updated: May 21, 2021 02:38PM UTC

Thank you!!

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.