Welcome to our community!

Allow for a choice between legacy consent method and the newest one-time consent until restart method

JVergo

9 years ago
updated 9 years ago
Completed

The recent update changes the way consent to control works. Now, it only requires consent for the first time connecting, and allows for connecting to the machine over and over without consent there after until the session is ended, service started, or possibly with a reboot. The original method required consent each time the tech connects to that PC.

The new consent method is a huge HIPAA concern, especially with LabTech users using the ScreenConnect integration, as connecting this way does not allow for easily ending the session.

The resolution would be to give us the option to switch between the concent method, that way everybody is happy, and people who are invovled in HIPAA-sensitive environments do not need to explore moving away from ScreenConnect and opting for a different solution.

Duplicates 4

Parameter to configure how consent cache behaves

Arturo

We request a parameter to set up the longevity of guest consent and/or wether it is cached or not.

stored consent

stefan pirhofer

ScreenConnect Support: "That stored consent is hardcoded functionality in the system and it was changed in 5.6.if you would like the ability to have that consent appear everytime a host connects to a session then that would be a feature request"

In our environment we have many different access session groups. To guarantee the security we have setup different permissions on each access session group.Some with consent, some with out consent requirement. Since Version 5.6 a host which have been already accepted at guest client , is able to connect the next time without any guest consent. We would need an option to deactivat this "feature".

Change consent back to everytime instead of every session.

chris swanger

Change consent back to everytime instead of every session. The new way is not HIPAA com

user consent per access group and dialog be displayed on every connection

Michal

Partners are requesting that consent dialog must be displayed on every connection for security reasons..and will be nice to be able set consent only for one group, without manually adding lot of groups without consent. So i can add only one line to (for example) session_admin without adding too many lines for other groups.

Replies 21

Oldest first
Newest first Oldest first

anonymous

9 years ago

Michal, are you an on-premise or cloud partner?

Reply Link

Michal

9 years ago

Hi, on-premise.

Reply Link

Roudger

9 years ago

Yes, since version 5.6, after a first connection, consent dialog not displayed until the machine is rebooted or the service cycles.it would be nice to have an option to force the display of consent dialog each time.

Reply Link

MikeLGS

9 years ago

Any news of this from the dev team? Due to privacy concerns, we can't update ScreenConnect to version 5.6 unless this has been fixed.

Reply Link

Mike Bannerman Team Member

9 years ago
Under Review

Link

anonymous

9 years ago

Making the option configurable in this manner doesn't address the overall issue. There were a lot of requests to make consent survive a reboot of the machine. Dev is currently looking at alternatives that should work for both use cases. I'll try to update this post when I have new information.

Link

Jonathan Yergo

9 years ago

Having the ability to control when consent is "reset" is very important for SC users that manage HIPAA environments. Though a pain for some, for healthcare clients, its important that SC asks for consent every time a tech connects to a client workstation, even if the session is already established.

Having some comprehensive consent control options could make everybody happy in that consent requirements could be better customized depending on the environment. Even further, it would beneficial to be able to assign workstations to different "consent groups" in the case one workstation falls under HIPAA requirements but another may not.

Reply Link