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: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-42626

Sensitive information displayed in anonymous REST API calls

      Expected behavior

      Block sensitive information from being displayed on anonymous REST API calls in JIRA.

      Actual behavior

      • Users' full-name are displayed when running the calls below:
        /user/picker?query=<username>
        /groupuserpicker?query=ali&showAvatar
        
      • Default fields and custom fields are displayed when running the call below:
        /jql/autocompletedata
        

      Workaround

      There's no current method for working around this within JIRA itself. The only solution would be to setup IP filtering on affected calls.

            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: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-42626

            Sensitive information displayed in anonymous REST API calls

                Expected behavior

                Block sensitive information from being displayed on anonymous REST API calls in JIRA.

                Actual behavior

                • Users' full-name are displayed when running the calls below:
                  /user/picker?query=<username>
                  /groupuserpicker?query=ali&showAvatar
                  
                • Default fields and custom fields are displayed when running the call below:
                  /jql/autocompletedata
                  

                Workaround

                There's no current method for working around this within JIRA itself. The only solution would be to setup IP filtering on affected calls.

                        ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
                        jpalharini Joao Palharini (Inactive)
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        10 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
                            jpalharini Joao Palharini (Inactive)
                            Affected customers:
                            0 This affects my team
                            Watchers:
                            10 Start watching this issue

                              Created:
                              Updated:
                              Resolved: