starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 23:15:57 +03:00

[GH-ISSUE #580] agent.logged_in_user variable not working #2314

New issue

Closed

opened 2026-03-14 03:32:55 +03:00 by kerem · 5 comments

kerem commented

2026-03-14 03:32:55 +03:00

Owner

Originally created by @eric-robbins on GitHub (Jun 16, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/580

Server Info (please complete the following information):

OS: Ubuntu 20.04
Browser: chrome, FireFox
RMM Version (as shown in top left of web UI): v0.6.15

Installation Method:

Standard

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI): v1.5.8
Agent OS: Win 10

Describe the bug
The agent.logged_in_user variable doesn't work.

To Reproduce
Steps to reproduce the behavior:

Create a script with argument -logged_in_user {{agent.logged_in_user}}.
Add content of:
Param (
[string]$logged_in_user
)
Write-Host "The logged in user is: $logged_in_user"
Output is:
The logged in user is: {agent.logged_in_user}

Expected behavior
Should get output of:
The logged in user is: someUserName

Screenshot

Additional context
I have tested with all other agent variables as listed at https://wh1te909.github.io/tacticalrmm/script_variables.html. All other variables work except {{agent.logged_in_user}}. I have made sure to go back and use a copy past method with the agent variable to assure that there is no typo etc.

Originally created by @eric-robbins on GitHub (Jun 16, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/580 **Server Info (please complete the following information):** - OS: Ubuntu 20.04 - Browser: chrome, FireFox - RMM Version (as shown in top left of web UI): v0.6.15 **Installation Method:** - [x] Standard **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): v1.5.8 - Agent OS: Win 10 **Describe the bug** The agent.logged_in_user variable doesn't work. **To Reproduce** Steps to reproduce the behavior: 1. Create a script with argument -logged_in_user {{agent.logged_in_user}}. 2. Add content of: Param ( [string]$logged_in_user ) Write-Host "The logged in user is: $logged_in_user" 3. Output is: The logged in user is: {agent.logged_in_user} **Expected behavior** Should get output of: The logged in user is: someUserName **Screenshot** ![image](https://user-images.githubusercontent.com/39501983/122252613-1c946880-ce91-11eb-8162-dbcc7010e986.png) **Additional context** I have tested with all other agent variables as listed at https://wh1te909.github.io/tacticalrmm/script_variables.html. All other variables work except {{agent.logged_in_user}}. I have made sure to go back and use a copy past method with the agent variable to assure that there is no typo etc.

kerem closed this issue

2026-03-14 03:33:00 +03:00

kerem commented

2026-03-14 03:33:06 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jun 16, 2021):

Hi, thanks this is actually a typo in the docs. should be {{agent.logged_in_username}} just pushed an update to the docs
not all the variables are documented, you can always check the models.py file in each django app to get the full list of available vars (assuming they're not like json fields) github.com/wh1te909/tacticalrmm@99f2772bb3/api/tacticalrmm/agents/models.py (L46)

@wh1te909 commented on GitHub (Jun 16, 2021): Hi, thanks this is actually a typo in the docs. should be `{{agent.logged_in_username}}` just pushed an update to the docs not all the variables are documented, you can always check the `models.py` file in each django app to get the full list of available vars (assuming they're not like json fields) https://github.com/wh1te909/tacticalrmm/blob/99f2772bb39ecb87c52046668cfe7bc16d079e80/api/tacticalrmm/agents/models.py#L46

kerem commented

2026-03-14 03:33:11 +03:00

Author

Owner

@silversword411 commented on GitHub (Jun 16, 2021):

@wh1te909 Adding my todo list to update all the items in models.py to the docs. Should I skip the #Deprecated ones?

@silversword411 commented on GitHub (Jun 16, 2021): @wh1te909 Adding my todo list to update all the items in models.py to the docs. Should I skip the #Deprecated ones?

kerem commented

2026-03-14 03:33:17 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jun 16, 2021):

@silversword411 awesome ty, yea skip the deprecated ones and also skip any of the models.JSONField since those won't render properly as strings

@wh1te909 commented on GitHub (Jun 16, 2021): @silversword411 awesome ty, yea skip the deprecated ones and also skip any of the `models.JSONField` since those won't render properly as strings

kerem commented

2026-03-14 03:33:22 +03:00

Author

Owner

@silversword411 commented on GitHub (Jun 16, 2021):

....also, if I re-arrange all those items (under class Agent(BaseAuditModel):) into alphabetic order it's not going to break anything is it? eg

operating_system = models.CharField(null=True, blank=True, max_length=255)
salt_ver = models.CharField(default="1.0.3", max_length=255)
version = models.CharField(default="0.1.0", max_length=255)

@silversword411 commented on GitHub (Jun 16, 2021): ....also, if I re-arrange all those items (under `class Agent(BaseAuditModel):`) into alphabetic order it's not going to break anything is it? eg ``` operating_system = models.CharField(null=True, blank=True, max_length=255) salt_ver = models.CharField(default="1.0.3", max_length=255) version = models.CharField(default="0.1.0", max_length=255) ```

kerem commented

2026-03-14 03:33:27 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jun 16, 2021):

best to leave it as is, cuz changing stuff in the models will trigger a database migration which should only happen if we add or delete new db fields

@wh1te909 commented on GitHub (Jun 16, 2021): best to leave it as is, cuz changing stuff in the models will trigger a database migration which should only happen if we add or delete new db fields

kerem referenced this issue

2026-03-14 07:13:47 +03:00

[GH-ISSUE #2314] Customizable Columns in RMM Clients View #3373