We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-5816

Add global public API accessToken config

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.7.0
    • None
    • backend
    • None
    • Not defined

      Context:
      As more and more public APIs are added we decide to consolidate the accessToken(s) together into one shared config, see https://camunda.slack.com/archives/CNSMT82SJ/p1639386771001800

      AT:

      • a global accesstoken config is used by all public APIs of Optimize, see https://docs.camunda.org/optimize/develop/technical-guide/rest-api/
        • there is already an existing config property to be used being api.optimizeAccessToken
      • the following accessToken configs are removed from the documentation:
        • eventBasedProcess.eventIngestion.accessToken
        • externalVariable.variableIngestion.accessToken
        • export.json.accessToken
      • the following accessToken configs are marked as deprecated:
        • eventBasedProcess.eventIngestion.accessToken
        • externalVariable.variableIngestion.accessToken
      • there is no automatic access token generation in case the value is set to `null` but instead api calls will be blocked (as already done for export.json.accessToken
      • the documentation is adjusted accordingly

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'Camunda Optimize'
            1. Camunda Optimize
            2. OPT-5816

            Add global public API accessToken config

              • Icon: Task Task
              • Resolution: Fixed
              • Icon: L3 - Default L3 - Default
              • 3.7.0
              • None
              • backend
              • None
              • Not defined

                Context:
                As more and more public APIs are added we decide to consolidate the accessToken(s) together into one shared config, see https://camunda.slack.com/archives/CNSMT82SJ/p1639386771001800

                AT:

                • a global accesstoken config is used by all public APIs of Optimize, see https://docs.camunda.org/optimize/develop/technical-guide/rest-api/
                  • there is already an existing config property to be used being api.optimizeAccessToken
                • the following accessToken configs are removed from the documentation:
                  • eventBasedProcess.eventIngestion.accessToken
                  • externalVariable.variableIngestion.accessToken
                  • export.json.accessToken
                • the following accessToken configs are marked as deprecated:
                  • eventBasedProcess.eventIngestion.accessToken
                  • externalVariable.variableIngestion.accessToken
                • there is no automatic access token generation in case the value is set to `null` but instead api calls will be blocked (as already done for export.json.accessToken
                • the documentation is adjusted accordingly

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        sebastian.bathke Sebastian Bathke
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              sebastian.bathke Sebastian Bathke
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              1 Start watching this issue

                                Created:
                                Updated:
                                Resolved: