The usage of the keystore location is missleading

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 2.3.0-alpha1, 2.3.0
    • Affects Version/s: None
    • Component/s: backend

      • given:
        • I want to change the keystore used for https certificate validation
      • when:
        • I set an absolute path
        • and I start Optimize
      • then:
        • Optimize is still using the default keystore
      • expected:
        • Optimize checks if it can find the keystore file as an absolute location.
        • If not, it searches in the classpath
        • this behavior is described in the documentation and the comments of the config files

      Hint:
      We should also check, if the keystore exists for an absolute file, we should also check if we have the rights to read it and if not log that as a warning to the user.

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: