Control anonymous user access

You can configure Jira to restrict anonymous user access and protect your data from being viewed by users that aren't logged-in. Oftentimes, anonymous users can access your data if you have filters or dashboards set to be viewed publicly or you have the Browse users global permission granted to the Anyone group. Shared publicly and Anyone in these cases mean anyone from in and outside your organisation.

Proper configuration can:

I want to know if my instance has public facing content

1. Check whether pubic sharing is ON.

In order to identify if your instance has content that is open for the public you first need to confirm if the Sharing with anyone on the web functionality is ON. If your Jira instance is private and not to be used by users without logging in you should turn this feature OFF. This way users will no longer be able to share any dashboards or filters with anonymous users.

This feature is OFF by default.


Jira administrators can disable the option of Jira users to share dashboards and filters publicly. To disable this option do the following. 

  1. Go to  > System > General Configuration
  2. Click Edit Settings
  3. Select OFF in Sharing with anyone on the web. 
  4. Click Update.

Turning the feature off will not affect existing filters and dashboards. If you change this setting, you will still need to update the existing filters and dashboards if they have already been shared publicly.

If you've still chosen to allow sharing with anyone on the web in some circumstances you can set the default preference for your users to private so that they can't accidentally grant public access to dashboards or filters.

To set the default sharing for filters and dashboards:

  1.  > Jira settings > System.
  2. Choose Default user preferences and select Edit default values.
  3. Set Default access to Private and click Update.
2. Get the list of existing public filters and dashboards.

Even if you've disabled sharing with anyone on the web, this does not update existing filters and dashboards. To confirm if there are any filters or dashboards shared with the public we can run the SQL queries below.

Identify public facing filters & dashboards ...
Always  back up  your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.


Filters

Get the list of all filters of the "AShare with anyone on the web" share type (i.e. global).

SELECT sr.filtername, sp.sharetype AS current_share_state, sr.username AS owner_name, sr.reqcontent AS JQL
FROM searchrequest sr
INNER JOIN sharepermissions sp ON sp.entityid = sr.id 
WHERE sp.sharetype='global' and sp.entitytype ='SearchRequest';

Alternatively go to > System > Shared Items > Shared filters and look for any filters with the Shared with anyone on the web status in the Shared with column.

Dashboards

Get the list of dashboards of the "share with everyone" share type (i.e. global).

SELECT DISTINCT pp.id as Dashboard_Id, pp.pagename AS Dashboard_name, sp.sharetype AS current_share_state, pp.username AS owner_name
FROM portalpage pp
INNER JOIN sharepermissions sp ON sp.entityid = pp.id 
WHERE sp.sharetype='global' and sp.entitytype ='PortalPage'
ORDER BY pp.id;

Alternatively go to > System > Shared Items > Shared dashboards and look for any dashboards with the Shared with anyone on the web status in the Shared with column.

3. Monitor the Browse User global permission

Through the user picker functionality within Jira your user base information could be available to anonymous users. The Browse User Global Permission allows a user to view a list of all Jira user names and group names, share issues, and @mention people on issues. This is used for selecting users/groups in popup screens and also enables auto-completion of user names in most 'User Picker' menus and popups.

If you grant this permission to the Anyone on the web group, you will be allowing anonymous users access to the endpoints that provide a list of users.


Ensure that this permission is restricted to specific groups that require it. You can restrict it in  > System > Global Permissions.

I want to restrict all my public facing content

1.Update your existing public filters and dashboards

To restrict you public facing filters and dashboards, change the sharing configuration for the filters manually. To change filters in bulk, you need to perform an update through a DB query.

First, make sure you've turned off public sharing and identified content that is currently shared publicly.

2. Review the global Browse Users permission

Ensure that this permission is restricted to specific groups that require it.

  • Go to  > System > Global Permissions.

  • Go to the "Browse Users" permission under Jira Permissions.

  • Remove the group "Anyone on the web" from this permission.

3. Review search engines crawlers access

See the document Using robots.txt to hide from search engines on how to control access from search engines.

After you restrict certain pages from Search Engine crawlers, the information that has already been cached by search engines may take a few days to become unavailable. There is no way to instantly remove all cached information from search engines besides contacting the service provider (e.g. Google) directly. You may need to provide evidence that you're the owner of the content that you're requesting to take down.


4. Block all anonymous access

You can use a dark feature to disable site-wide anonymous access was introduced. For more on dark features, see Enable dark feature in Jira.

Enable the dark feature to disable public access

  1. Login as an administrator and go to [BASE-URL]/secure/SiteDarkFeatures!default.jspa.
  2. In the Enable Dark Feature text field add public.access.disabled.
Last modified on Sep 10, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.