infrastructure-notes/archive/jira-sucks.md

Post upgrade foo

*** IMPORTANT ***

The salt state jira now stages an update and performs all of the below tasks. After runnign the state, the only thing that needs to be updated is /etc/init.d/jira

See msoc-infrastructure/salt/fileroots/jira/README.md for details.

IGNORE THE REST. THIS IS THE MANUAL WAY TO DO WHAT SALT NOW TAKES CARE OF FOR YOU.

Summary

A JIRA upgrade will flat-out replace a bunch of files that you have customized. They recommend that you re-apply your customization to the new files instead of trying to port your new files forward. It's rather messy, the worst part being the OKTA integration which is kinda nasty.

Update conf/server.xml

Add the reverse proxy fun to the port 8080 connector stanza

proxyName="jira.mdr.defpoint.com" proxyPort="443" scheme="https" secure="true"/>

Put in okta bits

• Re-add okta-jira-3.1.3.jar to /opt/atlassian/jira/atlassian-jira/WEB-INF/lib
• Re-add okta_login.jsp to /opt/atlassian/jira/atlassian-jira
• Re-add okta-config-jira.xml to /opt/atlassian/jira/conf

Put in okta bits part 2

Okta explains it better than I can. There's some web.xml filter setting that need to be in place.

https://mdr-multipass-admin.okta.com/app/jira_onprem/0oa1pvluodtaQH3Ee297/setup/help/SAML_2_0/instructions