Summary

Anonymous users cannot see JIRA Sprint events in Team Calendars, even if they have the necessary permissions in JIRA and in the Confluence space.

Steps to Reproduce

1. Install JIRA 7.0 or above
2. Install Confluence 5.10.3
3. Install Team Calendars 5.3.16
4. Create an application link between JIRA and Confluence
5. Create a project in JIRA and grant the Browse Projects permission to group Anyone in the permission scheme assigned to that project.
6. Create a sprint in JIRA
7. Create a space in Confluence
8. In the space permissions for that space, grant Anonymous access to view the space
9. Create a calendar in Team Calendars
10. Add a JIRA Sprint Event from the project you created in step 5
11. Embed this calendar in a page on the publicly accessible space you created in step 7
12. Logout of Confluence
13. Access Confluence without logging in and navigate to the page on which the calendar is embedded.

Expected Results

You should be able to see all events displayed on the calendar, including the sprint events from JIRA.

Actual Results

None of the JIRA events are displayed and you see an error message at the top of the page as shown in the screenshot below:

Unable to load events of Test Project - Sprints (102e6464-e274-4e3b-9284-82f526b363ef): calendar3.error.jiraresponse

The following error appears in the log:

2017-03-06 15:27:36,781 ERROR [http-nio-8090-exec-8] [extra.calendar3.rest.AbstractResource] getEvents Unable to load events of sub-calendar 102e6464-e274-4e3b-9284-82f526b363ef
 -- referer: http://<IP>:8090/display/TS/Calendar+Test+page | url: /rest/calendar-services/1.0/calendar/events.json | traceId: b9bd63294fac9e66 | userName: anonymous
2017-03-06 15:27:36,785 ERROR [http-nio-8090-exec-8] [jersey.spi.container.ContainerResponse] logException Mapped exception to response: 500 (Internal Server Error)
 -- referer: http://<IP>:8090/display/TS/Calendar+Test+page | url: /rest/calendar-services/1.0/calendar/events.json | traceId: b9bd63294fac9e66 | userName: anonymous
javax.ws.rs.WebApplicationException

Workaround

There is no workaround at this time.