Microsoft AD v2 spoke "Add Users to Group" failing with error from AD containing trailing square bracket "]" in the username - Support and Troubleshooting

Microsoft AD v2 spoke "Add Users to Group" failing with error from AD containing trailing square bracket "]" in the username Issue Microsoft AD v2 spoke Add Users to Group fails with "Error: Invalid resource name: USERNAME], the username has a trailing square bracket and the username with trailing "]" does not exist in active directory.

By enabling the FLOW designer debugging properties , the below message can be seen in the flow context

{ "Step Status": { "code": 1, "message": "Error: Invalid resource name : XXX] (Process Automation.471b33823bfd5e50262fe6c036e45a7f; line 39)" } }

SEVERE *** ERROR *** Encountered error executing instruction: OpInstruction{id=6, opClass=com.snc.process_flow.operation.script.ScriptOperation, io=Io{input={mid_selection=RefOrValue{value=auto_select, isRef=false}, capabilities=RefOrValue{value=, isRef=false}, responseBody=RefOrValue{value=s2o.output, isRef=true}, mid_server=RefOrValue{value=, isRef=false}, group_name=RefOrValue{value=s1o.group_name, isRef=true}, mid_cluster=RefOrValue{value=, isRef=false}, errorMessage=RefOrValue{value=s2o.error_message, isRef=true}, mid_selection_type=RefOrValue{value=any, isRef=false}, script=RefOrValue{value=(function execute(inputs, outputs) { function handleError(error_message) { var errMessage = error_message; var resource_name; var actionErrors = { CANT_FIND_OBJECT: "Cannot find an object with identity" }; var commErrors = { AUTH_FAILURE: "Authentication failure with the user", SERVER_UNAVAILABLE: "The RPC server is unavailable", UNREACHABLE_STATUS: "Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied." }; var errorMessages = { INVALID_OBJECT_IDENTITY: "Invalid resource name", CREDENTIALS_FAILED: "Invalid credentials for host", ACCOUNT_LOCKED_OUT: "The referenced account is currently locked out and may not be logged on to", INVALID_HOST: "Invalid hostname in connection or host not reachable from MID Server", AUTH_FAILED_WITH_MID: "Host credentials incorrect. Authentication error in MID Server" }; if (error_message.indexOf(commErrors.AUTH_FAILURE) != -1) error_message = errorMessages.CREDENTIALS_FAILED; else if (error_message.indexOf(actionErrors.CANT_FIND_OBJECT) != -1) { resource_name = (error_message.split("' under:"))[0]; resource_name = (resource_name.split("identity: '")[1]).trim(); if (resource_name == inputs.group_name) { error_message = "Invalid Group Name : " + resource_name; } else if ((inputs.user_names).indexOf(resource_name) != -1) { error_message = "Invalid User Name : " + resource_name; } else { error_message = errorMessages.INVALID_OBJECT_IDENTITY + " : " + resource_name; } } else if (error_message.indexOf(commErrors.SERVER_UNAVAILABLE) != -1) error_message = errorMessages.INVALID_HOST; else if (error_message.indexOf(commErrors.UNREACHABLE_STATUS) != -1) error_message = errorMessages.AUTH_FAILED_WITH_MID; throw new Error(error_message); } if (inputs.errorMessage) handleError(inputs.errorMessage); else { var responseBody = JSON.parse(inputs.responseBody); if (responseBody.status != "Success") if (responseBody.body) handleError(responseBody.body); else handleError("Unknown error. Check error log for more information"); } })(inputs, outputs);, isRef=false}, connection_alias=RefOrValue{value=, isRef=false}, application=RefOrValue{value=35aa573fd7802200bdbaee5b5e610375, isRef=false}, required_run_time=RefOrValue{value=instance, isRef=false}, user_names=RefOrValue{value=s1o.user_names, isRef=true}, host=RefOrValue{value=, isRef=false}}, output={__step_status__=s3o.__step_status__}, defaultOutput={}}, name=471b33823bfd5e50262fe6c036e45a7f, parentActionId=9efcd35a87f159107701ed3e0ebb3517} com.snc.process_flow.exception.OpException: Error: Invalid resource name : XXX] (Process Automation.471b33823bfd5e50262fe6c036e45a7f; line 39) Cause The root cause is identified as PRB1788405, which is a known bug in the Microsoft Active Directory V2 Spoke version 2.2.0.

Resolution Option 1: The issue is fixed with the Microsoft Active Directory V2 Spoke plugin version 2.2.1

(or)

Option 2: Deploy the att ached update set that contains the workaround for PRB1788405. After deploying the update set, test the "Add users to Group" AD spoke action again.