Filter and Issues page not redirected after integrating JIRA with SSL or HTTPS

Still need help?

The Atlassian Community is here for you.

Ask the community

This article only applies to Atlassian's server products. Learn more about the differences between cloud and server.

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

  1. The web.xml does not contain <url-pattern>/issues/*</url-pattern>
  2. A suggestion ticket to update the documentation has been raised here  JRA-59871 - Getting issue details... STATUS

Resolution

  1. First ensure that JIRA has been correctly configured to run over SSL or HTTPS as per Running JIRA over SSL or HTTPS
  2. 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>

    (info) Notice that <url-pattern>/issues/*</url-pattern> is not included in Running JIRA over SSL or HTTPS which resolves this issue. 

  3. Restart JIRA

 

 

Last modified on Nov 2, 2018

Was this helpful?

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