Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-5133 As a User, I can use Token-Based Authentication to Elasticsearch by using a Plugin Mechanism
  3. OPT-5257

Allow insertion of authorization headers through a configured plugin

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.5.0-alpha2, 3.5.0
    • None
    • backend
    • None
    • Not defined

      Similar to our other plugins, we should add an interception point before we make requests to ES, allowing configured plugins to add headers to the request. This will support the use case for token-based authentication, but removes Optimize from the process of requesting or even understanding the tokens.

      ATs:

      • A plugin can be configured to add a custom authorization header to all ES requests
      • Optimize is a kind of dumb client to this plugin. If ES rejects requests as a result of an added header, Optimize is not expected to handle this scenario (it will log error outputs in any case)

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: