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 21
we are worried about our login page being hacked. and in this instance the hacker would have access to ALL our unattended access machines. E.g. if someone hacked our Administrator password. this is a MUST for us. we are already using ScreenConnect but it is a serious worry for us.
It appears SSAE16 requires this. We are awaiting our auditors to confirm but a per device password seems to be the consensus of what is required.
It appears SSAE16 requires this. We are awaiting our auditors to confirm but a per device password seems to be the consensus of what is required.
I know this topic shows under review but would like to add that the lack of this feature will likely be a game changer for us.
My company supports our products that are sold to hospitals (Private sector and US Gov related).
We are currently undergoing SSAE16 and may have to abandon ScreenConnect if we cannot get an idea of if/when this could be implemented.
I do NOT want to use any other product but other products out there are compliant.
We are new to ScreenConnect, and coming from LogMeIn Rescue. the security for access connections, is simply to weak. an idea could be, add two factor authentication to the access connections. so the user connecting to the access connection has to type there google authenticator code before being able to connect. or like logmein, require username and password authentication for the access connection.
Because of the limited security on the access connections, i can't allow our techs to use this function.
This is the one thing I miss from LMI. I liked the secondary auth using the Windows admin credentials that were always different from the LMI account credentials. I too worry about unfettered access to my client's systems should my self-hosted SC instance get hacked. I already use 2FA for login but that doesn't help much if a direct vulnerability is found in SC and exploited. Please add the feature as an optional one that can be turned on and by default allow any admin level account on the host to be used automatically.
Ditto! We must have this. If we walk away from our computer while logged in, or if someone hacks me, they can get into any computer in my Access Groups. LogMeIn has it, and you are much more feature-rich, but neglecting this important feature. I see this has been requested for over 2 years?!?!? I should have checked this before we purchased the year. You guys just must write this in.
Simply have each computer with it's own password that must be typed after double-clicking it.
Thanks
we ended using a config i cant remember atm.
what is does is it locks the machine you are connecting to. in doing this you need at lease the password to one of the user accounts on the machine you are connecting to or any domain user account if domain join setup ofcourse.
by doing it this way, we dont risk outsiders accessing machines or servers we can access with our Connectwise Control. a work around for sure, but it gets the job done until someone at connectwise assigns this issue to a DEV.
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