Contradictory behavior in log in Jira/Confluence 8.7.1 on Linux

[Giuseppe_Valter_Diurno]

Hello, 

  I have installed JIRA on my server which has a public IP address. I also have Confluence and bitbucket. I use a hostname associated to the IP address which is saved in the /etc/hosts file on the server, however in order to access the system from outside and from different computers, I have used the link with the IP address, thus clients are not forced to modify their hosts. 

When I login in Jira, I expect to seamlessly navigate to Confluence and Bitbucket but I always get the request for a new login. The second problem is that when I go back from Confluence to Jira, the application tries to open the URL hostname:port ,instead of IP:port and when I login again, I don't have access to Projects and all the content that is usually available. 

I checked the setting in Confluence , I am using IP:port as main URL, my questions, to take effect shall I restart Confluence ? How can I a have a global login instead of 3 different login ? 

[Mike Rathwell]

Hi there,

There are a whole bunch of things to unpack here so I will try to get enough of them to get you going

1. It is probably a bad idea to rely on a hostname stored only in the /etc/hosts file especially if your environment is publicly visible. You should have a DNS entry for those hosts and set the base URL for all applications to the hostname
2. As delivered, Jira, Confluence, and Bitbucket have separate user bases. You can configure all of them to use Jira as the user authority but that does not preclude having to log into each of them; rather that just gives you a common username/password pair. To not auth on each of them, you would need to do a SAML login from some other authority
   1. A note on the above: On all of them, even with separate user bases, if you have the application links correctly set up and you log into all 3 with checking the "remember me" button, you can go smoothly via the application navigator
3. You note IP:port; does this mean you are hitting the default 8XXX port as delivered from Atlassian? If so, you should probably do some further configuration one each of them and/or get them behind a proxy server of some kind (like NGINX)
4. Your problem with Jira and not getting to where you think is likely driven by mismatches in all of the above: /etc/hosts doesn't match the IP address and the Base URL set in the application doesn't match any of them. Consistent naming of the target including the Base URL is extremely important for all three of these applications. An attempt to mix/match IP:port, hostname, hostname:port for methods of getting to them will not go well.