Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2026-11-13
Set Up Live Data Query in DBeaver

Set Up Live Data Query in DBeaver

Through a JDBC connection, Live Data Query enables SQL access from DBeaver to Workday business objects.
  1. In DBeaver, add a driver to the Driver Manager.
    1. Configure the following details in the
      Settings
       tab:
      Option
      Description
      Driver Name
      Enter a name for the LDQ driver.
      Driver Type
      Generic
      Class Name
      com.workday.ldq.jdbc.api.LDQJdbcDriver
      URL Template
      jdbc:workday://{HOST}:{PORT}
      Default Port
      443
    2. Leave all other fields in the
      Settings
       tab as default.
    3. In the
      Libraries
       tab, upload the .jar file you downloaded in the Prerequisites section.
    4. Click
      Find Class
       to verify the driver class is detected.
      Ensure
      com.workday.ldq.jdbc.api.LDQJdbcDriver
       appears in the driver class dropdown.
  2. Create a new database connection using the driver you created above.
    1. In the
      Connection Settings
      , select
      Main
      Connect by URL
      , and enter details relevant to the authorization flow you’re using:
      ISU
      User-As-Self
      JDBC URL
      jdbc:workday://{HOST}:443
      Replace
      {HOST}
       with the
      {HOST1}
       value from the Token Endpoint created in the Live Data Query ISU setup.
      jdbc:workday://{HOST}:{PORT}?SSLVerification=NONE
      Replace:
      • {HOST}
         with the
        {HOST1}
         value from the Token Endpoint created in the User-As-Self Authentication setup.
      • {PORT}
         with 443.
    2. On the
      Driver Properties
       tab, add the properties relevant to the authorization flow you’re using:
      Property
      ISU
      User-As-Self
      wd.authn.authModel
      JWT_BEARER
      AUTHORIZATION_CODE
      wd.authn.clientId
      Client ID created in the Live Data Query ISU setup.
      Client ID created in the User-As-Self Authentication setup.
      wd.authn.clientSecret
      N/A
      Client secret created in the User-As-Self Authentication setup.
      wd.authn.isu
      Your ISU.
      N/A
      wd.authn.accessTokenEndpoint
      Token endpoint created in the Live Data Query ISU setup.
      Example:
      https://{HOST1}/ccx/oauth2/{TENANT}/token
      Token endpoint created in the User-As-Self Authentication setup.
      Example:
      https://{HOST1}/ccx/oauth2/{TENANT}/token
      wd.authn.authorizationEndpoint
      N/A
      Authorization endpoint created in the User-As-Self Authentication setup.
      Example:
      https://{HOST2}/{TENANT}/authorize
      wd.authn.privateKeyFilePath
      The full path of the private key file.
      • Windows Example:
        C:\Users\user.name\Documents\{privateKeyFile.txt}
      • Mac Example:
        /Users/path/to/your/private_key.pem
      For a Windows machine, you must specify the
      wd.authn.privateKeyFilePath
       property.
      The
      wd.authn.privateKey
       and
      wd.authn.privateKeyFilePath
       properties are mutually exclusive. If you specified
      wd.authn.privateKey
      , don’t specify
      wd.authn.privateKeyFilePath
      .
      N/A
      wd.authn.privateKey
      The
      wd.authn.privateKey
       and
      wd.authn.privateKeyFilePath
       properties are mutually exclusive. If you specified
      wd.authn.privateKey
      , don’t specify
      wd.authn.privateKeyFilePath
      .
      We recommend using
      wd.authn.privateKeyFilePath
       for LDQ in DBeaver.
      Privacy-Enhanced Mail (PEM) format text. Must include the header/footer.
      For information about the private key, see Generate Public and Private Keys for Workday Live Data Query.
      N/A
      wd.authn.redirectUrl
      N/A
      https://localhost:8888/callback
    3. If you use a Single Sign-On, you must log in to your Workday tenant using your default browser before you attempt to connect. This only applies to user-as-self authentication.
      Click
      Test Connection
       to verify the configuration.
      A successful test results in a
      Connected
       message. When there are errors, verify that the driver properties and connection settings are configured correctly.
    4. Save the connection.
  3. Connect (User-As-Self authentication only).
    1. Double-click the new connection.
      DBeaver will trigger the OAuth flow, automatically opening your default browser on the Workday login page.
    2. Log in with your Workday credentials and approve access.
      The browser redirects to
      https://localhost:8888/callback
      .
    3. A browser security warning may appear because the callback server uses a self-signed certificate. Accept the warning to proceed (this is expected — the certificate is local to your machine).
      You have 5 minutes to complete the browser login. If you exceed this, the connection attempt fails and you can retry.
    4. Once the browser shows a success message, return to DBeaver. The connection completes automatically.
  4. Execute a query.
    1. In the
      Database Navigator
      , expand the new connection.
    2. Right-click the connection and select
      SQL Editor
      New SQL Script
      .
    3. Enter the query
      select count(*) from workday_core.public.worker
       in the SQL Editor and click
      Execute
       to run it.
      The response should appear in the bottom half of the pane.
Run queries against your Workday data. See Query Workday Data Using Live Data Query.