Uploaded image for project: 'JITL - JobScheduler Integrated Template Library'
  1. JITL - JobScheduler Integrated Template Library
  2. JITL-600

JITL Job CheckHistory should support use of a Credential Store

    XMLWordPrintable

Details

    • Fix
    • Status: Released (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.12, 1.13
    • 1.12.13, 1.13.4
    • None

    Description

      Current Situation

      The JITL Job JobSchedulerCheckHistoryJSAdapterClass reads the credentials for the JOC webservice and the url for the JOC webservice from a the file $scheduler_data\config\private\private.conf

      joc.webservice.jitl{
      joc.account="cm9vdDpyb290"
      joc.url = "http://localhost:4446"
      }
      

      Values for these parameters are specified as plain text and therefore can be read for everybody with access to this file.

      Desired Behavior

      It should be possible to read the values for user, password url and any other parameters from a keepass credential store.

      There are the following parameters needed to specify the key store.

      • The file name of the keystore: Mandatory
      • The file name of the keyfile: Optional if missing the filename like credential_store_file but with .key as extension will be used
      • The password for the key store: Optional. Only needed when the keyfile has a password.
      • The path for in the keystore: Optional to make the cs:// value shorter.

      There are two sources (private.conf and credentialStore) for the parameters. When both are given, the values from the credential store are used.

      1. as query parameters in the value e.g. cs://....?file=value%password=value
      2. as explicit parameters in the job or order
        • credential_store_file: The name of the keepass credential store file
        • credential_store_key_file: The name of the keepass credential store file.
        • credential_store_password: The password for the keepass credential store file or empty
        • credential_store_entry_path: The default path for the entries
      • Exampel for a job that make use of query parameters
        • user = cs://some/path/entry@user?credential_store_file=credentials.kdbx
        • password = cs://some/path/entry@password?credential_store_file=credentials.kdbx
        • joc_url = cs://some/path/entry@url?credential_store_file=credentials.kdbx

      Attachments

        Issue Links

          Activity

            People

              Aditi-Dubey Aditi Dubey (Inactive)
              ur Uwe Risse
              Aditi Dubey Aditi Dubey (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: