What is a one sentence summary of your feature request?
When a Task Automation activity is used, Privilege Secure should not generate or expose an RDP file to the end user, as this undermines the hands-off, zero-touch intent of the activity type.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Currently, when a Task Automation based activity is configured and a session is launched, Privilege Secure still generates an RDP file that the requesting user can download and use directly. This is inconsistent with the core purpose of Task Automation activities, which are designed to execute predefined tasks without requiring or permitting interactive access by the user.
The ability to retrieve and use an RDP file effectively bypasses the controlled, automated nature of the activity and could allow users to gain interactive desktop access to resources that should only be touched programmatically. This is a meaningful gap in the access control model for organisations relying on Task Automation to enforce least privilege.
How do you currently solve the challenges you have by not having this feature?
Proposed behaviour:
For activities of type Task Automation, the RDP file generation should be suppressed entirely. The user should have no ability to download or use an RDP file for sessions initiated under this activity type.
Why this matters:
Organisations use Task Automation activities precisely because they want automated, auditable, and non-interactive access to resources. Exposing an RDP file to the user contradicts that intent and introduces an uncontrolled access vector that may not align with internal security policies or compliance requirements.