Error, spontaneous user change

Question

Good day. We have Jira DC 10.3.2 installed. For some time, an error has been constantly observed: a user who is authorized under his account, which is synchronized via the LDAP catalog, at some point in time is transferred to a completely different account. Example: I log in under the test1 login, work for 15-20 minutes and after a while I find that I am authorized under the test2 account, while I do not know either the login or the password for test2 and I have not completed authorization in it. What could be the reason for this behavior?

Philipp Sendek _catworkx_ · Answer

Thanks for the clarification!

This sounds like you're not even operating two nodes but one single Jira node. In that case, my assumption doesn't apply that the session mix up might happen during switch between nodes.

In that case, all I can suggest is to confirm that your nginx configuration is exactly as provided by Atlassian and if that's the case, I would recommend you to create a ticket with Atlassian support so they can help you troubleshoot the issue. You can file a ticket here: https://support.atlassian.com/contact/
I hope they'll be able to help you solve it.

Greetings
Philipp

David Armstrong_snbnbz · Answer

Thanks for the reply. The application server is located on the same server. There are no load balancers. Users connect simply via the Internet, without using a VPN. The network scheme looks like this:

router >npm (nginx proxy manager)>server with jira.

All users use their devices to connect

Philipp Sendek _catworkx_ · Answer

Hi @David Armstrong ,

welcome to the community. This is a very strange behaviour I haven't come across yet.
It might be an issue in Jira, but I would rule it out for now, as this would have made news quite quickly.
It looks like the session tokens are somehow mixed up leading to one user adopting the session of another user.

Do you have access and overview of your Jira's architecture? Especially, how many nodes you have and the load balancer that sits before Jira and manages the routing to a node.
If so, I would suggest to start with checking the configuration and troubleshooting it with some test users to see if for some reason, it could happen that session-ids and node associations are mixed up and - after 15 - 20 minutes - people are by accident routed to a different node where they adopt the session id of another user. (As I'm not deeply involved in the topic how session ids are generated, this is a guess that might make no sense at all - but we have to start somewhere. :-))

Also, taking a look at the client side: How are your users - or the specifically affected users - accessing Jira? Do they have their own hardware? Are they in the same office or at least using the same VPN? Or are they accessing it using virtual desktop environments?

Greetings
Philipp