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-6136

Remove accounts service fallback request on cache miss

    • 1
    • S

      When a user is added to the collection in SaaS mode, a text string can be entered to find that user. If the user doesn't match a search result in Optimze's cache, the request is forwarded to the accounts service. However, this doesn't make sense as cloud users can never know their ID, and the ID is the only means for retrieving users at this endpoint.

      Optimize should instead not allow this secondary fetching, and only allow the addition of users that do exist in the cache.

      Notes:

      • These requests were highlighted as erroneous by the cloud team. In the case of many requests, it could even cause an issue of preventing use of the accounts service
      • The implication of this change is that users can only be added to a collection if they do exist in a cache. New users may have to wait until the cache is repopulated before they are granted access to collections
      • If these requests are shown to be causing problems, it might be that we need to provide a patch for this going forward

        This is the controller panel for Smart Panels app

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

            Remove accounts service fallback request on cache miss

              • 1
              • S

                When a user is added to the collection in SaaS mode, a text string can be entered to find that user. If the user doesn't match a search result in Optimze's cache, the request is forwarded to the accounts service. However, this doesn't make sense as cloud users can never know their ID, and the ID is the only means for retrieving users at this endpoint.

                Optimize should instead not allow this secondary fetching, and only allow the addition of users that do exist in the cache.

                Notes:

                • These requests were highlighted as erroneous by the cloud team. In the case of many requests, it could even cause an issue of preventing use of the accounts service
                • The implication of this change is that users can only be added to a collection if they do exist in a cache. New users may have to wait until the cache is repopulated before they are granted access to collections
                • If these requests are shown to be causing problems, it might be that we need to provide a patch for this going forward

                  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:

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

                                Created:
                                Updated:
                                Resolved: