Details
-
Suggestion
-
Resolution: Fixed
-
None
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Problem Definition
After connecting JIRA to SSL or HTTP as per
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.
Suggested Solution
Adding :
<url-pattern>/issues/*</url-pattern>
to the <web-resource-collection> on the web.xml file. This is not documented on :
It would be great if this documentation is updated to :
<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>
Attachments
Issue Links
- relates to
-
JRACLOUD-59871 Documentation : Filter and Issues page not redirected after integrating JIRA with SSL or HTTPS
- Closed
- mentioned in
-
Page Loading...