Active Directory package updates

Review the updates in released versions of the Active Directory package such as new and enhanced features as well as fixes and limitations. The page also lists the release dates of each version, and the compatible Control Room and Bot Agent versions.

Versions summary

The following table lists the versions of Active Directory package released either with an Automation 360 release or as a package-only release (in descending order of release dates). Click the version link for information about updates in that package version.

Version Release date Release type Bot Agent version Control Room build
3.11.1 15 October 2025 Package-only; post Automation 360 v.38 release 20.11 or later 8750 or later
3.10.0 5 March 2025 With Automation 360 v.36 (Sandbox) release 20.11 or later 8750 or later
3.9.0 6 September 2023 With Automation 360 v.30 (Sandbox) release 20.11 or later 8750 or later
3.8.0 6 June 2023 With Automation 360 v.29 (Sandbox) release 20.11 or later 8750 or later
Note:
  • To download an individual package (updated in an Automation 360 release where you want only the package), use this URL:

    https://aai-artifacts.my.automationanywhere.digital/packages/<package-file-name>-<version.number>.jar

  • For Active Directory package, the naming convention is: bot-command-activedirectory-<version.number>.jar

    For example, bot-command-activedirectory-3.9.0.jar

For detailed steps on downloading a package and manually adding it to the Control Room, see Add packages to the Control Room.

3.11.1

  • Compatible Bot Agent version: 20.11 or later
  • Compatible Control Room version: 8750 or later
What's new
LDAPS support in Active Directory package (Service Cloud Case ID: 00769067, 02114863, 02151436, 02229146, 02274387)

We introduce support for LDAPS (Lightweight Directory Access Protocol over SSL), which enables secure and encrypted communication between the application and LDAP directory services. LDAPS enhances data protection and complies with enterprise security standards by utilizing SSL/TLS protocols.

Add LDAPS server certificate to Windows certificate store | Using Connect action for Active Directory | Using the Move computer action | Using the Move organizational unit action | Using the Add users to group action | Using the Remove users from group action

3.10.0

  • Compatible Bot Agent version: 20.11 or later
  • Compatible Control Room version: 8750 or later
Fix
Fixed security vulnerability issues. For more information, click the release download link and view the Security & Compliance reports at A-People Downloads page (Login required).

3.9.0

  • Compatible Bot Agent version: 20.11 or later
  • Compatible Control Room version: 8750 or later
What's changed

Help Center for bot developers

  • Help Center: We have added an in-app help for bot developers to get contextual information about actions and packages when building automations.
  • Added intuitive icons for actions in a package.
Fix
The following issues in the package are fixed:
  • You can use the Rename user action to rename the user logon name or the user name.
  • You can use the Rename group action to rename an existing group.

3.8.0

  • Compatible Bot Agent version: 20.11 or later
  • Compatible Control Room version: 8750 or later
Fixes
In the Active Directory package, when you use user names with special DN (distinguished names) characters such as semicolon (;), hash sign (#), equal (=), plus (+), less than/greater than (< >), or backslash (\), the bot now runs successfully.

Previously, when you add a user to a group and if the user name had special characters, the bot failed when you tried to remove the user from the group.
When you create bots using the Run query action from the Active Directory package, it retrieves the complete object name even if the name contains special characters such as (or \).

Previously, it retrieved partial object name when the name contained special characters such as (or \).

Service Cloud case ID: 01924111