We have seen an issue where in some scenarios, it may be possible to connect to a user’s screen without requiring their acceptance. When you initially establish a jump session and perform Shell work to fix an issue, users may have their screen locked or logged out. Unfortunately, the session policies do not appear to re-evaluate, so whatever the status of the device was when you established the jump session is held throughout the session.
A workaround would be to disconnect the jump session and establish a fresh session before you use the screenshare function, which would then pick up the user is logged on and present the prompt.
For example:
User reports an issue on desktop, walks away.
The machine is connected to (Shell, System etc but not screen sharing).
User returns and unlocks the machine.
Screen sharing is started from the Rep Console.
Due to the existing session already established (using Shell and System Information), no prompt for the user to accept is required, and it connects to the screen.
To mitigate this, Rep Console users would need to log out and back in to it, before attempting a screen share.
It seems like the session should be re-evaluated each time a new method of connection is established - would be good to know if this feature is planned or if there is another way to achieve this which doesn’t rely on the Console user logging out and back in again? Thanks.
