Automate install with custom Maven repos and authentication

[peterpk]

Hi! I am working on a Powershell script to download and install DBeaver CE automatically, and point it to our company's internal Maven repository mirrors. So far I've been able to download and expand the release archive (.ZIP), start it once by command line to initialize the user workspace folders, and then copy in new maven-repositories.xml files pointing to our repos.

The problem is that our repos require authentication, with userid and identity token. I can get those in my script, but putting them into the XML files does not seem to work -- DBeaver is still prompting for the ID and password. I saw in the source that DBeaver expects the password to be encrypted, so I tried doing so based on some old code in the Git history, but it still doesn't work.

In addition to the fact that DBeaver is asking for the id and password, I can see an IOException in the debug log, where it is trying to connect to our private mirrors. Unfortunately, the exception message is simply "null".

I could, of course, instruct each user to go into the Driver settings and fill in their ID and token manually, but I'd much rather have it fully automated if possible. Has anyone tried doing something like this? Is there a better way I could prefill the authentication info?

Thanks!

[rameshreddy-adutla]

DBeaver CE stores its Maven/P2 repository configuration in the dbeaver.ini and workspace metadata. Here's how to automate it with PowerShell:

1. Silent install (Windows):

# Download and install silently
Start-Process -FilePath "dbeaver-ce-latest-x86_64-setup.exe" -ArgumentList "/S" -Wait

2. Configure custom Maven repos — edit the workspace preferences file:

$prefsPath = "$env:APPDATA\DBeaverData\workspace6\.metadata\.plugins\org.jkiss.dbeaver.core\dbeaver.ini"
# Or for global driver settings:
$driversPath = "$env:APPDATA\DBeaverData\workspace6\.metadata\.plugins\org.jkiss.dbeaver.core\drivers.xml"

3. For authenticated Maven repos, you can create a maven-settings.xml and point DBeaver to it:

• Go to Window → Preferences → DBeaver → Drivers → Maven in the GUI to see the format
• The settings are stored in $APPDATA/DBeaverData/workspace6/.metadata/.plugins/org.jkiss.dbeaver.core/ as XML
• You can pre-populate these files before first launch

4. Alternatively, pre-download the JDBC drivers and configure local paths:

$driversDir = "$env:APPDATA\DBeaverData\drivers"
New-Item -Path $driversDir -ItemType Directory -Force
Copy-Item "your-driver.jar" -Destination $driversDir

Then configure the driver path in DBeaver's driver manager to point to the local JAR.

This approach avoids the need for Maven authentication entirely during DBeaver runtime.

[peterpk]

Sorry, it has been a while since I could come back to look at this. Unfortunately, this hasn't helped me. I'm using the ZIP files to do a manual install, and then I was already able to successfully plug in our custom Maven repository addresses (as in your step 2). However, the custom maven-settings.xml file to add in passwords did not work. I tried something like this:

<repository id="Corp-Maven-JCentral" order="5" enabled="true" url="https://my.company.com/artifactory/Maven-JCentral/" name="Corp-Maven-JCentral" auth-user="USERNAME_HERE" auth-password="API_KEY_HERE"/>

but the auth-user and auth-password fields were ignored. I was hoping to get more information by setting the id and password manually through the UI, but that did not change the maven-repositories.xml file at all. Does DBeaver store saved passwords somewhere more secure?