Skip to content

Active Directory considerations and settings

Resilio 6.0 Enterprise Hybrid Work deployments require Active Directory services to be configured and available for end user Agents authentication and user impersonation.

Requirements and considerations

The following are Active Directory recommendations and best practices for Resilio 6.0 Enterprise Hybrid Work deployments:

  • Management Console and the Primary Storage Agent must be in the same domain.
  • End user Agents in multiple Active Directory domains
    To allow end user Agents to authenticate using accounts from multiple domains, users outside the domain that the Management Console is deployed in, must be in a Global or Universal scope group as external Domain Local scope groups cannot be queried.

    In case of end user Agents deployed in different domains (including domains in different forests), ensure that the Management Console and the Primary Storage Agent are deployed in a domain that has two-way (incoming and outgoing) trust relationships with other domains. For more information, see How trust relationships work for forests in Active Directory.

    Foreign Security Principal objects

    Management Console cannot list Foreign Security Principal (FSP) objects within a group. If you have a group, containing users from other trusted domains as Foreign Security Principal objects, Management Console won't be able to access those users and add them to the Job. You must assign users and groups from each domain (group-centric scanning mode) or forest (agent-centric scanning mode) separately.

  • User accounts properties
    User accounts in Active Directory must have UserPrincipalName (UPN) property assigned. UPN is used for delegation (impersonation) and to link users between OpenID providers (Entra ID, Okta) and Active Directory. Users without UPN assigned cannot participate in Enterprise Hybrid Work Jobs. The presence of the UPN can be verified in user management UI or with PowerShell command:

    Get-ADUser user_a -Properties SID,UserPrincipalName,DistinguishedName
    
  • Scanning and synchronizing Active Directory users and groups
    Adjust the scanning mode and interval to ensure that the list of users entitled to access Resilio services is up to date. For more information, see Scanning and synchronizing Active Directory users and groups.

  • Agents re-authentication
    Agents connected to the Management Console via Active Directory authentication require periodic re-authentication to ensure that the user account is still valid and has the necessary permissions. The re-authentication interval can be configured in the Management Console's configuration file. For more information, see Agent re-authentication.

Scanning and synchronizing Active Directory users and groups

Active Directory scanning modes

Resilio periodically scans and synchronizes users and groups from Active Directory, to ensure that the list of users entitled to access Resilio services is up to date. Resilio offers two options for scanning and synchronizing Active Directory users and groups:

  • Agent-centric – Iterates over each Agent and scans groups in the AD forest that the user account belongs to. This option is suitable for organizations with up to 1000 end user Agents.
  • Group-centric – Iterates over each domain group and checks against known end user Agents within a single domain scope. Group-centric scanning is more efficient for organizations with over 1000 end user Agents.

    Note

    Initial group-centric scanning may take longer time to complete compared to subsequent periodic scans.

Change Active Directory scanning mode

To change the Active Directory scanning mode:

  1. Open the Management Console's configuration file.
  2. In the adAgentAuth object, set the agentCentricRefresh parameter to true for agent-centric scanning or false for group-centric scanning (default).

    Tip

    Add the adAgentAuth object and the agentCentricRefresh parameter if they don't exist in the configuration file.

    "adAgentAuth": {
        "domainGroupRecheckInterval": 900000,
        "domainAuthedConnectionLifetime": 14400000,
        "agentCentricRefresh": false
    }
    

Change Active Directory scanning interval

To change the Active Directory scanning interval:

  1. Open the Management Console's configuration file.
  2. In the adAgentAuth object, change the domainGroupRecheckInterval parameter to the desired interval in milliseconds (default is 900000 or 15 minutes).

    Tip

    Add the adAgentAuth object and the domainGroupRecheckInterval parameter if they don't exist in the configuration file.

    "adAgentAuth": {
        "domainGroupRecheckInterval": 900000,
        "domainAuthedConnectionLifetime": 14400000,
        "agentCentricRefresh": false
    }
    

Applying changes to Active Directory users to live end user Agents

Based on the periodic Agent-centric scan results, end user Agents are automatically disconnected if their accounts are no longer present in Active Directory. If the scan identifies change in user account information, that change is reflected in the end user Agent information stored on the Management Console.
You can also disconnect and enforce end user Agent re-authentication if the Agent authentication configuration changes. To do that, enable the Require re-authorization on configuration change option in Agent authentication settings for the authentication method you're using.

Agent re-authentication

Agents connected to the Management Console via Active Directory authentication require periodic re-authentication to ensure that the user account is still valid and has the necessary permissions. The re-authentication interval can be configured in the Management Console's configuration file.

To change end user Agents re-authentication interval:

  1. Open the Management Console's configuration file.
  2. In the adAgentAuth section, set the value of the domainAuthedConnectionLifetime parameter to the desired interval in milliseconds (default is 14400000 or 4 hours).

    Tip

    Add the adAgentAuth object and the domainAuthedConnectionLifetime parameter if they don't exist in the configuration file.

    "adAgentAuth": {
        "domainGroupRecheckInterval": 900000,
        "domainAuthedConnectionLifetime": 14400000,
        "agentCentricRefresh": false
    }
    

Agent reauthentication grace period and timeout

When the re-authentication interval is reached, the Management Console sends a request for the end user Agent to re-authenticate. The end user Agent is expected to initiate re-authentication within 30 seconds grace period (gracePeriod) and must complete it within 2 minutes (timeout). If the end user Agent fails to initiate re-authentication within the grace period or complete it within the timeout, the end user Agent is disconnected from the Management Console.

Note

The authentication timeout counter starts when the end user Agent begins re-authentication, not when the Management Console sends the re-authentication request. In worst case scenario, the end user Agent may have up to 2 minutes and 30 seconds to complete re-authentication.

To change the grace period or the timeout value:

  1. Open the Management Console's configuration file.
  2. In the agentReauth section, set the gracePeriod and timeout parameters to the desired values in milliseconds (defaults are 30000 or 30 seconds for gracePeriod and 120000 or 2 minutes for timeout).

    Tip

    Add the agentReauth object and the gracePeriod and timeout parameters if they don't exist in the configuration file.

    "agentReauth": {
        "timeout": 120000,
        "gracePeriod": 30000
    }