Filter and Issues page not redirected after integrating JIRA with SSL or HTTPS
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
After integrating JIRA with SSL or HTTPS , old urls for filters and issues that are still using the HTTP protocol is not properly redirected to HTTPS.
When trying to access those HTTP or non SSL urls for the filters or issues
- User is logged out of JIRA
- Page not redirected to the new HTTPS link as it should.
Cause
- The
web.xml
does not contain<url-pattern>/issues/*</url-pattern>
- A suggestion ticket to update the documentation has been raised here - JRA-59871Getting issue details... STATUS
Resolution
- First ensure that JIRA has been correctly configured to run over SSL or HTTPS as per Running JIRA over SSL or HTTPS
Add this snippet on the <JIRA-INSTALL>/atlassian-jira/WEB-INF/web.xml file right above </web-app>
<security-constraint> <web-resource-collection> <web-resource-name>all-except-attachments</web-resource-name> <url-pattern>*.jsp</url-pattern> <url-pattern>*.jspa</url-pattern> <url-pattern>/browse/*</url-pattern> <url-pattern>/issues/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint> </security-constraint>
Notice that
<url-pattern>/issues/*</url-pattern> is not included in
Running JIRA over SSL or HTTPS which resolves this issue.- Restart JIRA