Burp Suite User Forum

Login to post

Burp Enterprise unattended install -- what is the administrator password?

John | Last updated: Sep 13, 2019 11:04PM UTC

When doing an unattended install from a response file generated by a previous install, e.g. `./burpsuite_enterprise_linux_v1_1_02.sh -q -varfile response.varfile`, what's the administrator password set to? The password from the previous installation is not saved to response.varfile.

Mike, PortSwigger Agent | Last updated: Sep 16, 2019 09:39AM UTC

Hi, when you install Burp Suite Enterprise you are required to specify the credentials for the administrator account, we don't have any default values for this. You can create a new administrator by running a utility that should be in the installation directory called ‘adminusercreator’. An example of how to run it is: adminusercreator —username=new_admin —password=letmein —email=some@example.com —dbUrl=jdbc:<your database url> —dbUsername=burp_enterprise —dbPassword=*

Burp User | Last updated: Sep 16, 2019 03:16PM UTC

What's the dbUrl format if you chose the file-based internal database?

Mike, PortSwigger Agent | Last updated: Sep 16, 2019 03:24PM UTC

Hi John, glad I could help and thank you for sharing your solution.

Burp User | Last updated: Sep 16, 2019 03:39PM UTC

Figured it out, I had to stop the burpsuiteenterpriseedition_db service then use: adminusercreator --username=administrator --password=newpassword --email=security@example.com --dbUrl=jdbc:h2:/var/lib/BurpSuiteEnterpriseEdition/data/burpsuiteenterpriseedition_db --dbUsername=burp_enterprise --dbPassword=[redacted] (where dbPassword was found in /opt/burpsuite_enterprise/database/init.sql) Thanks

Jay | Last updated: Feb 14, 2020 07:49PM UTC

With burpsuite_enterprise_linux_v2020_1.sh I am not getting prompted to enter credentials for the administrator account. And when I attempt to run: /opt/burpsuite_enterprise/adminusercreator —username=administrator —password=letmein —email=email@company.com —dbUrl=jdbc:dbaname:3306/burpenterprise —dbUsername=xxxxx —dbPassword=xxxxx I get a "password is mandatory" response.

Ben, PortSwigger Agent | Last updated: Feb 18, 2020 10:19AM UTC

Hi Jay, Are you using two hyphen characters when specifying each parameter (the formatting on your post suggests you are using the — character)?

Jay | Last updated: Feb 19, 2020 07:47PM UTC

yes, that was it. I copied the script from above & didn't notice the different characters. thanks.

John | Last updated: Feb 25, 2020 04:08PM UTC

When I run the adminusercreator utility I get the following: # ./adminusercreator --username=new_admin --password=<password> --email=me@example.com --dbUrl=jdbc:<my DB>.us-east-2.rds.amazonaws.com:5432/burpenterprise --dbUsername=beserver --dbPassword='<beserver password>' Create admin user on URL:jdbc:<my DB>.us-east-2.rds.amazonaws.com:5432/burpenterprise, User: beserver 15:51:29.838 [main] INFO net.portswigger.enterprise.common.repository.b - Creating data source for URL: jdbc:<my DB>.us-east-2.rds.amazonaws.com:5432/burpenterprise, username: beserver 15:51:29.842 [main] INFO net.portswigger.enterprise.common.repository.b - DB timeouts: idle=60000, max life=120000 15:51:29.855 [main] DEBUG com.zaxxer.hikari.HikariConfig - bewspool - configuration: 15:51:29.861 [main] DEBUG com.zaxxer.hikari.HikariConfig - allowPoolSuspension.............false 15:51:29.862 [main] DEBUG com.zaxxer.hikari.HikariConfig - autoCommit......................true 15:51:29.862 [main] DEBUG com.zaxxer.hikari.HikariConfig - catalog.........................none 15:51:29.862 [main] DEBUG com.zaxxer.hikari.HikariConfig - connectionInitSql...............none 15:51:29.862 [main] DEBUG com.zaxxer.hikari.HikariConfig - connectionTestQuery.............none 15:51:29.862 [main] DEBUG com.zaxxer.hikari.HikariConfig - connectionTimeout...............10000 15:51:29.862 [main] DEBUG com.zaxxer.hikari.HikariConfig - dataSource......................none 15:51:29.862 [main] DEBUG com.zaxxer.hikari.HikariConfig - dataSourceClassName.............none 15:51:29.862 [main] DEBUG com.zaxxer.hikari.HikariConfig - dataSourceJNDI..................none 15:51:29.863 [main] DEBUG com.zaxxer.hikari.HikariConfig - dataSourceProperties............{password=<masked>} 15:51:29.863 [main] DEBUG com.zaxxer.hikari.HikariConfig - driverClassName.................none 15:51:29.864 [main] DEBUG com.zaxxer.hikari.HikariConfig - healthCheckProperties...........{} 15:51:29.864 [main] DEBUG com.zaxxer.hikari.HikariConfig - healthCheckRegistry.............com.codahale.metrics.health.HealthCheckRegistry@a514af7 15:51:29.864 [main] DEBUG com.zaxxer.hikari.HikariConfig - idleTimeout.....................60000 15:51:29.864 [main] DEBUG com.zaxxer.hikari.HikariConfig - initializationFailFast..........false 15:51:29.864 [main] DEBUG com.zaxxer.hikari.HikariConfig - initializationFailTimeout.......-1 15:51:29.864 [main] DEBUG com.zaxxer.hikari.HikariConfig - isolateInternalQueries..........false 15:51:29.864 [main] DEBUG com.zaxxer.hikari.HikariConfig - jdbc4ConnectionTest.............false 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - jdbcUrl........................."jdbc:<my DB>.us-east-2.rds.amazonaws.com:5432/burpenterprise" 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - leakDetectionThreshold..........0 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - maxLifetime.....................120000 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - maximumPoolSize.................10 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - metricRegistry..................com.codahale.metrics.MetricRegistry@6b927fb 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - metricsTrackerFactory...........none 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - minimumIdle.....................0 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - password........................<masked> 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - poolName........................"bewspool" 15:51:29.865 [main] DEBUG com.zaxxer.hikari.HikariConfig - readOnly........................false 15:51:29.866 [main] DEBUG com.zaxxer.hikari.HikariConfig - registerMbeans..................false 15:51:29.866 [main] DEBUG com.zaxxer.hikari.HikariConfig - scheduledExecutor...............none 15:51:29.866 [main] DEBUG com.zaxxer.hikari.HikariConfig - scheduledExecutorService........internal 15:51:29.866 [main] DEBUG com.zaxxer.hikari.HikariConfig - threadFactory...................internal 15:51:29.866 [main] DEBUG com.zaxxer.hikari.HikariConfig - transactionIsolation............"TRANSACTION_READ_COMMITTED" 15:51:29.866 [main] DEBUG com.zaxxer.hikari.HikariConfig - username........................"beserver" 15:51:29.866 [main] DEBUG com.zaxxer.hikari.HikariConfig - validationTimeout...............5000 15:51:29.868 [main] INFO com.zaxxer.hikari.HikariDataSource - bewspool - Starting... net.portswigger.enterprise.common.config.l: Problem creating driver class at net.portswigger.enterprise.common.repository.ax.a(Unknown Source) at net.portswigger.enterprise.common.repository.ax.a(Unknown Source) at net.portswigger.enterprise.common.repository.b.<init>(Unknown Source) at net.portswigger.enterprise.common.repository.b.<init>(Unknown Source) at net.portswigger.enterprise.server.adminuser.AdminUserCreator.main(Unknown Source) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:85) at com.install4j.runtime.launcher.UnixLauncher.main(UnixLauncher.java:62) Caused by: java.lang.RuntimeException: Failed to get driver instance for jdbcUrl=jdbc:<my DB>.us-east-2.rds.amazonaws.com:5432/burpenterprise at com.zaxxer.hikari.util.DriverDataSource.<init>(DriverDataSource.java:88) at com.zaxxer.hikari.pool.PoolBase.initializeDataSource(PoolBase.java:323) at com.zaxxer.hikari.pool.PoolBase.<init>(PoolBase.java:114) at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:105) at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:72) at net.portswigger.enterprise.common.repository.ax.a(Unknown Source) ... 10 more Caused by: java.sql.SQLException: No suitable driver at java.sql/java.sql.DriverManager.getDriver(DriverManager.java:299) at com.zaxxer.hikari.util.DriverDataSource.<init>(DriverDataSource.java:81) ... 15 more I am (pretty) sure my DB URL is correctly formatted but could be wrong. I can connect to the DB with the postgresql client from my burp instance. It looks like jdbc issues but I am not sure how to resolve.

John | Last updated: Feb 25, 2020 04:51PM UTC

<Apologies for double posting above> I found my problem. My DB was not being called properly. I left off the postgresql (--dbUrl=jdbc:<my DB>.us-east-2.rds.amazonaws.com:5432/burpenterprise as opposed to --dbUrl=jdbc:postgresql://<my DB>.us-east-2.rds.amazonaws.com:5432/burpenterprise)

Ben, PortSwigger Agent | Last updated: Feb 26, 2020 08:40AM UTC

Hi John, Glad to hear that you were able to resolve your issue. Please do not hesitate to get back in touch if you require assistance with anything else in the future.

You need to Log in to post a reply. Or register here, for free.