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

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

Construction pattern of  the 'Same Domain' 

If "'Confluence” user can access to "Alfreso one" on the Web Browser when URL are same domain as shown below.

• Confluence
  
  • https://aaa.com/confluence
• Alfresco one
  • https://aaa.com/share
    
  • https://aaa.com/alfresco
    

Connection settings for "Alfresco connector for Confluence" will be specified the URL with same domain as the "Confluence" as shown below.

•  1. "Alfresco connector for Confluence"- "Connection Setup" - "Alfresco Display URL"
  • https://aaa.com/alfresco
•  2. "Alfresco connector for Confluence"- "Connection Setup" - "Alfresco Application URL"
  • ttps://aaa.com/alfresco
    

Configuration type of 'Different Domains (Cross domain)'

If "Confluence" user can not access to "Alfresco one" on the Web Browser when URL are same domain as shown below...

• Confluence
  
  • https://ccc.com/confluence
• Alfresco one
  • https://bbb.com/share
    
  • https://bbb.com/alfresco

Connection settings for "Alfresco connector for Confluence" will be specified the URL with different domain as the "Confluence" as shown below.

•  1. "Alfresco connector for Confluence" - "Connection Setup" - "Alfresco Display URL"
  • https://bbb.com/alfresco
•  2. "Alfresco connector for Confluence" - "Connection Setup" - "Alfresco Application URL"
  • https://bbb.com/alfresco
    

But, the following 2 conditions must be.

But, the following 2 condition will be required.

•  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 cross domain（CORS)（English)