How to protect xaml code on client side

Help Studio
, ,
1

how to protect xaml code on client side its more required when we are on client side
if any has idea please share

2

HI @Bhargavi_Lokapur1

Some Simple Steps you can follow are:

  1. Publish as a Library: Publish your workflow as a library. This way, people can use the pre-built activities but won’t see the detailed XAML code.
  2. Encrypt Packages: When you publish, enable package encryption. It scrambles the XAML code, making it harder to read.
  3. Secure Sensitive Data: Don’t store sensitive information like passwords directly in your workflows. Use UiPath’s Credential Manager to keep them safe.
  4. Control Access: Limit who can access the XAML files. Set up permissions so only the right people can edit or view them.
  5. Use Version Control : Store your XAML files in a version control system. It helps track changes and control who can make them.
1 Like
3

Hi @Bhargavi_Lokapur1 ,
In client need run robot only, that’s right?
You can install Studio only,
Since they need to only RUN the code.
Ask them to install only UiPath Robot. Hence they wont be able to make any customization to your code.
Or you can create share folder, and not share roles edit it
regards,

4

in UiPath i want to the client does not use other pc and etc

5

Hi @Bhargavi_Lokapur1 ,
You can create new user, eg : client user
then share role access file and folder
in folder source with all of file code you can limit role of this user, this user can see only
regards,

1 Like
6

But anyone can go to folder then click on right side it will change the security easily

7

Hi @Bhargavi_Lokapur1

Here are some approaches and best practices to help you protect your XAML code on the client side:

  1. Use Orchestrator: Store your workflows in UiPath Orchestrator and restrict access to the Orchestrator portal. This way, the XAML files are not exposed directly to the client machines.
  2. Limit Access: Control physical access to client machines where workflows are deployed. Limit user access to the files and directories containing XAML files.
  3. Client-Server Model: Implement a client-server architecture where the actual automation logic resides on a server, and the client only sends requests. The server can keep the XAML files secure.
  4. Security Policies: Enforce strict security policies on client machines to prevent unauthorized access to the XAML files. Use file system permissions to restrict access.
  5. Monitoring and Auditing: Implement monitoring and auditing mechanisms to track who accesses the XAML files and what they do with them.

Thanks!

8

No You have admin user, you can share role edit for other user in this PC

regards,

9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.