unattended access password prompt separate from AD Authentication
TeamViewer, LogMeIn and BomGar have this and we would like this on ScreenConnect Side as well
Welcome to our community!
Duplicates 5
unattended connection to be able to have a password against it
Generate dynamic password
Dear, I want to have available the option to be able to execute a remote host with dynamic password, in this way the end user has the conformity and security that a connection is not established without its authorization.
Add PIN code to individual machines
Hi,
In LMI we could add PIN codes to individual machines to prevent authorized ScreenConnect users from connecting. I am hiding these machines via session groups and and/not logic trickery, but I'd love to just put a PIN on these machines and not worry about hiding them nor them becoming visible.
Can we add this as a feature?
Thanks,
Dave
unattended session passwords
I would like the ability to add a password to an unattended session. Currently you would have to add a password to ALL session I would like to see this at a session level instead of the wide sweeping level it is currently.
Allow single user access to personal home PC via screenconnect unattended access client with password
I work for a Company that uses ScreenConnect.
I want to install the ScreenConnect Unattended Access client on my Home PC and access remotely.
I want to restrict access to this home PC to myself only
Is it possible to put a password on the unattended access client?
Replies 22
This feature cannot be added fast enough.
Despite my technicians having the permission to access unattended machines I want any system we have deemed 'sensitive' to require an additional PIN on every connection to those machine.
As mentioned by others, it is now mid 2025 and this is an ~8 year old request and security is more important than ever.
I would even go so far to say that having an option to have a 'Sensitive' access 2FA app code (separate from login would be an option). In this case an option to have a unattended session protected by 2FA in order to access would be available. For illustration this feature can be called 'Sensitive Device.' A user with permission to access 'Sensitive Devices' would have a 2nd 2FA added to there account profile, when they attempt to access any device with the 'Sensitive Device' flag turned on they would be prompted to enter the 2FA app code.
Workflow would be...
Technician login -> password -> Login 2FA -> Access attempt to 'Sensitive Device' -> 'Sensitive Device' 2FA
Whatever method used, we need the ability to protect devices by additional pin/passcodes after successful authentication.
So this request has been consideration for more than 7 years now..
Come now Connectwise Control crew, we are in 2024 now, security is more then ever more important.
Please do more.
This has been a request for 8 years and has been in consideration for 7 years. Please allow us to add unattended password to select sessions or maybe they can have their own 2FA.
After seeing the recent issues with Kaseya - I would have thought that this should be one of the highest priorities - yet it's still remaining in the same state as it was 4 years ago... "pending review"
In this day and age with hacking becoming a greater threat, ransomware, cyber warefare, government operators, etc - it's not a matter of if, but when - and this is now not an option - it's a necessity.
Some customers don't feel "secure" they are asking us for a custom password like "teamviewer", so they can control their own password to access their PCs
Role based is not enough for them because it is in our end
My reasoning would be for what JaM added. We don't really need the password feature to have them on all the client machines. But we want to be able to set them so our IT users can't connect to each others machines.
This is a feature that should definitely be added, but make sure its implemented properly. Teamviewer can be a nightmare with their connection passwords.
Jake,
That does help a lot, so thanks for posting. However, still not as convenient as what we all are asking for, where we could just type a PW to get in upon connection. There is another reason for this, for example, I want my IT guy to have Admin access, but don't want him to be able to connect to my PC.
Thanks,
J
We have a config setting, MaxLongestTicketReissueIntervalSeconds, that is designed to provide very tight security and we believe addresses this issue in most (if not all) situations. MaxLongestTicketReissueIntervalSeconds will govern the longest period of inactivity since last login that is permissible to be able to perform an action. It's set to 36000 seconds (10 hours) by default, so set this to something like 300 seconds (5 minutes) or less in order to provide the security you're seeking. The benefit here is that it's not going to reprompt you upon joining each session as long as you've stayed active within the application. And it will protect you from unauthorized actions in the web UI such as sending commands (which are potentially more damaging than anything you can do inside a session).
FYI, you'll also have to change TicketReissueIntervalSeconds from the default of 600 seconds (10 minutes) to something less than your MaxLongestTicketReissueIntervalSeconds so that your session is continually extended while you're active in the application.
im the boss in our company and wanted a unattended connection to be able to have a pasword against it as i want a secure connection to my office pc that only i can use