In case of different FQDN between JIRA and Alfresco, our plugin does not connect to Alfresco appropriately due to 'Same Origin Policy', therefore JIRA and Alfresco should be connected by same FQDN from web browser.

However, 'Construction pattern of the different FQDN' prevents the policy and enables to connect correctly.

Construction pattern of the same FQDN

If 「JIRA」 user can access to 「Alfreso one」 with the URL of the same FQDN by Web Browser as shown below...

• JIRA
  • https://aaa.com/jira
• Alfresco one
  • https://aaa.com/share
    
  • https://aaa.com/alfresco

Connection settings 「Alfresco connector for JIRA」 will be specified the URL of the same FQDN as the JIRA as shown below.

•  1. 「Alfresco connector for JIRA」- 「Connection Setup」 - 「Alfresco Display URL」
  • https://aaa.com/alfresco
•  2. 「Alfresco connector for JIRA」- 「Connection Setup」 - 「Alfresco Application URL」
  • https://aaa.com/alfresco
    

Construction pattern of the different FQDN 

If 「JIRA」 user can not access to 「Alfreso one」 with the URL of the same FQDN by Web Browser as shown below...

• JIRA
  • https://ccc.com/jira
• Alfresco one
  • https://bbb.com/share
    
  • https://bbb.com/alfresco

Connection settings 「Alfresco connector for JIRA」 will be specified the URL of the different FQDN as the JIRA as shown below.

•  1. 「Alfresco connector for JIRA」 - 「Connection Setup」 - 「Alfresco Display URL」
  • https://bbb.com/alfresco
•  2. 「Alfresco connector for JIRA」 - 「Connection Setup」 - 「Alfresco Application URL」
  • https://bbb.com/alfresco

But, the following 2 conditions must be.

•  1. ReverseProxy for 「Alfresco one」 need to be Not Self-signed SSL certificate.
•  2. 「Alfresco one」's web.xml must be enabled CORS setting.
  1. Please see. Setup Guide for CORS (Cross-Origin Resource Sharing)