Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Current »

In case of different Origin(protocol, host, port) 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 Origin from web browser.  However, 'Construction pattern of the different FQDN' prevents the policy and enables to connect correctly.

Match Same Origin Policy

If the Origin (protocol, host, port) of the URL of "JIRA" and "Alfresco one" accessed by the user matches, You can access it as it is.

  • JIRA
    • https://aaa.com:80/jira
  • Alfresco one
    • https://aaa.com:80/share
    • https://aaa.com:80/alfresco
In this case, the Connection Setting of "Alfresco connector for JIRA" is as follows.

Does not Match Same Origin Policy 

If Origin (protocol, host, port) of the URL of "JIRA" or "Alfresco one" accessed by the user does not match, it can not be accessed as it is.

  • JIRA
    • https://ccc.com:80/jira
  • Alfresco one
    • https://bbb.com:80/share
    • https://bbb.com:80/alfresco
In this case, the Connection Setting of "Alfresco connector for JIRA" is as follows.

But, the following 2 conditions must be.

  • No labels