[GH-ISSUE #655] Full access to Mesh Commander after logging out of Tactical RMM #2363

Closed
opened 2026-03-14 03:43:13 +03:00 by kerem · 2 comments
Owner

Originally created by @epete99 on GitHub (Aug 8, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/655

Server Info (please complete the following information):

  • OS: [e.g. Ubuntu 20.04, Debian 10] Ubuntu 20.04
  • Browser: [e.g. chrome, safari] Chrome and Firefox (no access to Safari to check)
  • RMM Version (as shown in top left of web UI):

Installation Method:

  • Standard
  • Docker

Agent Info (please complete the following information):

  • Agent version (as shown in the 'Summary' tab of the agent from web UI):
  • Agent OS: [e.g. Win 10 v2004, Server 2012 R2]

Describe the bug
I setup a new Tactical RMM installation to test. I was able to log out of Tactical RMM and immediately log into Mesh with full access to all machines with no login credentials needed.

To Reproduce
Steps to reproduce the behavior:

  1. Log out of Tactical RMM
  2. In the same browser window, enter in the mesh URL
  3. Mesh was immediately logged in with no credentials needed
  4. Mesh allowed full access to all machines
  5. This does not occur when you close out of the browser

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Originally created by @epete99 on GitHub (Aug 8, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/655 **Server Info (please complete the following information):** - OS: [e.g. Ubuntu 20.04, Debian 10] Ubuntu 20.04 - Browser: [e.g. chrome, safari] Chrome and Firefox (no access to Safari to check) - RMM Version (as shown in top left of web UI): **Installation Method:** - [X] Standard - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): - Agent OS: [e.g. Win 10 v2004, Server 2012 R2] **Describe the bug** I setup a new Tactical RMM installation to test. I was able to log out of Tactical RMM and immediately log into Mesh with full access to all machines with no login credentials needed. **To Reproduce** Steps to reproduce the behavior: 1. Log out of Tactical RMM 2. In the same browser window, enter in the mesh URL 3. Mesh was immediately logged in with no credentials needed 4. Mesh allowed full access to all machines 5. This does not occur when you close out of the browser **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.
kerem closed this issue 2026-03-14 03:43:18 +03:00
Author
Owner

@dinger1986 commented on GitHub (Aug 8, 2021):

This is due to having used the login token via take control and remote background.

Logging out of tactical doesn't log you out of mesh as it's 2 separate systems.

I don't believe that can be changed

<!-- gh-comment-id:894798268 --> @dinger1986 commented on GitHub (Aug 8, 2021): This is due to having used the login token via take control and remote background. Logging out of tactical doesn't log you out of mesh as it's 2 separate systems. I don't believe that can be changed
Author
Owner

@wh1te909 commented on GitHub (Aug 17, 2021):

yea this is working as intended. You can play with mesh settings if you want to change it. I'm not really concerned with mesh settings other than the minimum settings required to get integration working.

<!-- gh-comment-id:899969305 --> @wh1te909 commented on GitHub (Aug 17, 2021): yea this is working as intended. You can play with mesh settings if you want to change it. I'm not really concerned with mesh settings other than the minimum settings required to get integration working.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#2363
No description provided.