We previously added a second ns entry in order to make our confluence Wiki accessable in another network and domain (using a proxy). So we got:
both of them are accessed and used, and it works. The Problem now are the JIRA Gadgets:
Because JIRA is in the int.bnc domain and in another network, there is no access via bnc.com.
If we make it accessible, what application link should I then set in order to make it work on both sites? I guess it is only possible to make this work for one URL because the application link only works with one.
In Addition the base-url now is 50% "wrong", and this is where i already had problem while setting up the JIRA gadgets.
If anyone did understand, is there a possible solution?
Jira and Confluence can only have ONE base url each. You need to use them on that one url.
Now, that only applies to the server side - if you have something in front of it, then you can rewrite the urls as much as you want (e.g. Apache), but you need to make sure that whenever does it always directs traffic to that one url.
Allright thank you Nic, I'll then configure the proxy to rewrite the url.
Now, while using those JIRA Gadgets over a Trusted Application Link, the requests to JIRA are sent from the client and not from the wiki instance, right? If so, if I acces
from the "outside" but both base urls point to <instance>.int.bnc. The bnc.com ones will be rewritten by the proxy.
Now I open a wiki page with JIRA Gadgets, but they are configured for jira.int.bnc where my client from outside doesn't know who this is, so again it will not work.
Long story short:
Thanks in advance
Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time! We're looking for people to participate in a remote 1-hr workshop...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs