Infra en robot connection questions

Help Robot
,
1

I have two questions regarding Infra & connecting robots:

  1. When do you use which connection type (machine key or client id)? Which is safer?
  2. Can IP whitelisting (allowlisting) be set up for Client systems?
2

  1. Connection Type (Machine Key or Client ID):

    • Machine Key: This is typically used when you want to establish a connection between UiPath Orchestrator and a specific robot on a machine. The machine key identifies the machine and allows robots installed on that machine to securely connect to Orchestrator. It’s suitable for dedicated machines where you want a one-to-one relationship between the machine and Orchestrator.

    • Client ID: Client ID is used when you want to create a connection between UiPath Orchestrator and a specific user or service, which might have multiple robots running on different machines. Client IDs are more flexible because they allow you to connect multiple robots under a single client ID. This is useful for scenarios where you have multiple robots on different machines but want to manage them collectively.

    The choice between machine key and client ID depends on your infrastructure and deployment requirements. Client ID can be a more flexible and scalable option, but it may not be suitable for situations where you need strict one-to-one relationships.

    As for safety, both machine keys and client IDs are secure when implemented correctly. It’s essential to follow best practices for securing the keys and credentials to prevent unauthorized access.

  2. IP Whitelisting (Allowlisting):

    UiPath Orchestrator supports IP whitelisting, allowing you to restrict access to Orchestrator services from specific IP addresses or ranges. This enhances security by controlling which machines and networks can communicate with Orchestrator.

    To set up IP whitelisting in UiPath Orchestrator:

    • Access Orchestrator and navigate to the Admin > Settings page.
    • In the “Networks” section, you can define the allowed IP addresses or IP address ranges.

    Keep in mind that while IP whitelisting can enhance security, it’s crucial to maintain and update the whitelist as your network configuration evolves. Be cautious when configuring IP restrictions to avoid inadvertently blocking legitimate connections.

    IP whitelisting is a valuable security measure, especially when dealing with sensitive data and restricted environments. It helps protect your Orchestrator instance from unauthorized access.

    Remember that implementing good security practices across your entire RPA infrastructure is crucial for maintaining the safety and integrity of your automation processes.

3

@ajay.malhi

  1. If you are creating machine templates then you would use client id and secret
  2. When creating standard machines then we can use machine key
  3. we can setup whitelisting for client systems thats your IT system admin work… and if it is allowed or not is a organization policy

cheers

4

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