We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-93552

When loading the "List of limited accounts" on the "Rate limiting" admin page, Anonymous user exceptions are removed

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 8.9.0
    • 8.5.0, 8.5.3
    • Data Center - Core
    • None

      Issue Summary

      When loading the "List of limited accounts" on the "Rate limiting" admin page, the anonymous user exception rules are deleted.

      This only occurs if the Anonymous user (Anonymous accounts) have been rate limited and are displayed on the "List of limited accounts" page. It will also remove the Anonymous user from the list.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Enable Anonymous access and rate limiting on your instance
      2. Add an Exception rule to block all requests for the Anonymous user
      3. Curl a rest API without authentication and receive "HTTP Status 429 – Too Many Requests"
      4. Wait a few minutes to ensure the data has been updated in the database
      5. Load the Rate limiting admin page and check the List of limited accounts for the user Anonymous

      Expected Results

      Anonymous user is in the List of limited accounts and the exception rule remains

      Actual Results

      Anonymous user is not in the List of limited accounts and the exception rule is removed

      Workaround

      Avoid loading the List of limited accounts after setting the exception rule

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Confluence Data Center'
            1. Confluence Data Center
            2. CONFSERVER-93552

            When loading the "List of limited accounts" on the "Rate limiting" admin page, Anonymous user exceptions are removed

              • Icon: Bug Bug
              • Resolution: Fixed
              • Icon: Low Low
              • 8.9.0
              • 8.5.0, 8.5.3
              • Data Center - Core
              • None

                Issue Summary

                When loading the "List of limited accounts" on the "Rate limiting" admin page, the anonymous user exception rules are deleted.

                This only occurs if the Anonymous user (Anonymous accounts) have been rate limited and are displayed on the "List of limited accounts" page. It will also remove the Anonymous user from the list.

                This is reproducible on Data Center: yes

                Steps to Reproduce

                1. Enable Anonymous access and rate limiting on your instance
                2. Add an Exception rule to block all requests for the Anonymous user
                3. Curl a rest API without authentication and receive "HTTP Status 429 – Too Many Requests"
                4. Wait a few minutes to ensure the data has been updated in the database
                5. Load the Rate limiting admin page and check the List of limited accounts for the user Anonymous

                Expected Results

                Anonymous user is in the List of limited accounts and the exception rule remains

                Actual Results

                Anonymous user is not in the List of limited accounts and the exception rule is removed

                Workaround

                Avoid loading the List of limited accounts after setting the exception rule

                        ephillips@atlassian.com Edward
                        ephillips@atlassian.com Edward
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            ephillips@atlassian.com Edward
                            ephillips@atlassian.com Edward
                            Affected customers:
                            1 This affects my team
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: