...
| Table of Contents | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Cause 1: Jira behind SSO or 2FA solution
See this dedicated support article related to Single Sign On solutions: Connect with SSO
Cause 2: App not installed in Jira
In case you are trying to logon to a private Jira Server or Data Center system from the Office add-in, and the corresponding app from the Marketplace is not installed, it might not work. In general, for licensing reasons it’s required to have the app installed anyway, so you’ll need to get in touch with your Jira administrator about this.
In case you still want to test first, before getting in touch, you can try using the COM add-in, which will allow you a 30 day trial without having anything configured in Jira (this only works if you don’t have any SSO installed).
...
Problematic headers your reverse proxy should not set on the response are:
Header | Value |
|---|---|
X-Frame-Options | SAMEORIGIN |
Content-Security-Policy | frame-ancestors 'self' |
As of Jira 7.6 these headers are not necessary anymore to add by the reverse proxy because Jira automatically sets them: https://confluence.atlassian.com/jirakb/security-headers-in-jira-939919914.html
Solution
...