[GH-ISSUE #503] MFA: Remember this device for 30 days #2257

Closed
opened 2026-03-14 03:15:09 +03:00 by kerem · 9 comments
Owner

Originally created by @davidrudduck on GitHub (May 12, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/503

This may be a conscious decision to enforce MFA checks upon EVERY login.

It would be great to have the ability to 'remember' the device so it's quicker to get back into when you're always on the same device.

Tell me to STFU if this is never going to happen ;)

Originally created by @davidrudduck on GitHub (May 12, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/503 This may be a conscious decision to enforce MFA checks upon EVERY login. It would be great to have the ability to 'remember' the device so it's quicker to get back into when you're always on the same device. Tell me to STFU if this is never going to happen ;)
kerem closed this issue 2026-03-14 03:15:14 +03:00
Author
Owner

@fred5632 commented on GitHub (May 13, 2021):

I agree, this is a nuisance

<!-- gh-comment-id:840184953 --> @fred5632 commented on GitHub (May 13, 2021): I agree, this is a nuisance
Author
Owner

@bradhawkins85 commented on GitHub (May 13, 2021):

This would be a really nice to have feature.
Would be good if the timeout was selectable though with options ranging from 1 hour to 30 days.

<!-- gh-comment-id:840190327 --> @bradhawkins85 commented on GitHub (May 13, 2021): This would be a really nice to have feature. Would be good if the timeout was selectable though with options ranging from 1 hour to 30 days.
Author
Owner

@saulens22 commented on GitHub (May 13, 2021):

A week sounds like a reasonable default for RMM tool

<!-- gh-comment-id:840343698 --> @saulens22 commented on GitHub (May 13, 2021): A week sounds like a reasonable default for RMM tool
Author
Owner

@frankemann commented on GitHub (May 13, 2021):

Even better would be a SSO with Azure Ad. We could then utilize Azure Ad Conditional Access based on our existing secutiry policies from ONE identity/device platform.

<!-- gh-comment-id:840401972 --> @frankemann commented on GitHub (May 13, 2021): Even better would be a SSO with Azure Ad. We could then utilize Azure Ad Conditional Access based on our existing secutiry policies from ONE identity/device platform.
Author
Owner

@davidrudduck commented on GitHub (May 13, 2021):

Maybe an option to set the timeout in hours, and you just do the math with the maximum value being 720 hours (30 days) or something?

<!-- gh-comment-id:840402031 --> @davidrudduck commented on GitHub (May 13, 2021): Maybe an option to set the timeout in hours, and you just do the math with the maximum value being 720 hours (30 days) or something?
Author
Owner

@wh1te909 commented on GitHub (May 13, 2021):

yea the auth token is hardcoded now to 5 hours TTL, with auto refresh happening every 600 seconds so basically if you leave your browser open forever with trmm logged in you'll never be logged out.

I can move this into local_settings.py and then you can just set it to whatever you want.

For now you can just edit settings.py which is in /rmm/api/tacticalrmm/tacticalrmm and look for this section github.com/wh1te909/tacticalrmm@67cc37354a/api/tacticalrmm/tacticalrmm/settings.py (L108)

and change the (hours=5) to (days=30) or whatever you want

then sudo systemctl restart rmm for changes to take effect. also log out and back in so token gets recreated

note settings.py will be overwritten on every rmm update but local_settings.py will not so next release i'll move it but for now just try the above and lmk if works

<!-- gh-comment-id:840402158 --> @wh1te909 commented on GitHub (May 13, 2021): yea the auth token is hardcoded now to 5 hours TTL, with auto refresh happening every 600 seconds so basically if you leave your browser open forever with trmm logged in you'll never be logged out. I can move this into `local_settings.py` and then you can just set it to whatever you want. For now you can just edit `settings.py` which is in `/rmm/api/tacticalrmm/tacticalrmm` and look for this section https://github.com/wh1te909/tacticalrmm/blob/67cc37354a18f8a310065fe55a44044cc9a95c76/api/tacticalrmm/tacticalrmm/settings.py#L108 and change the `(hours=5)` to `(days=30)` or whatever you want then `sudo systemctl restart rmm` for changes to take effect. also log out and back in so token gets recreated note `settings.py` will be overwritten on every rmm update but `local_settings.py` will not so next release i'll move it but for now just try the above and lmk if works
Author
Owner

@davidrudduck commented on GitHub (May 13, 2021):

Ah-may-zing ❤️

<!-- gh-comment-id:840403714 --> @davidrudduck commented on GitHub (May 13, 2021): Ah-may-zing ❤️
Author
Owner

@wh1te909 commented on GitHub (May 15, 2021):

released in 0.6.10 see https://wh1te909.github.io/tacticalrmm/functions/settings_override/ for instructions

<!-- gh-comment-id:841620431 --> @wh1te909 commented on GitHub (May 15, 2021): released in 0.6.10 see https://wh1te909.github.io/tacticalrmm/functions/settings_override/ for instructions
Author
Owner

@ventra007 commented on GitHub (Aug 16, 2022):

released in 0.6.10 see https://wh1te909.github.io/tacticalrmm/functions/settings_override/ for instructions

This link is dead. The new link is https://docs.tacticalrmm.com/functions/settings_override/

<!-- gh-comment-id:1216595458 --> @ventra007 commented on GitHub (Aug 16, 2022): > released in 0.6.10 see https://wh1te909.github.io/tacticalrmm/functions/settings_override/ for instructions This link is dead. The new link is https://docs.tacticalrmm.com/functions/settings_override/
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#2257
No description provided.