Getting Errors when adding User to an AD Group

EricG
Kilo Sage

Our group just got Integration Hub Professional and installed it to our environment.

I'm using the Microsoft AD SpokeV2 to add users to an existing AD Group.

 

It looks like this

EricG_0-1720552407327.png

In summation, I'm

1. Looking for the User in AD

1.a Lookup Group in AD

2. Once both are found, i then check if the are already a member of the Required Group.

2.a If Yes, then update ticket and close

2.b If Not, at the user to the group

3 If successful, then i close the ticket

4. Otherwise i assign the ticket to the appropriate group to complete manually.

 

Simple enough.

I've followed the On line documents and have my 4 domain credentials entered

along with my 3 domain connections. ( we have 3 different companies in out org.)

 

I'm using connection 1 to get to my TEST AD environment.

I'm able to find the user in Test AD, Validate the are not in the Group I've select.

But when I go to add them in the group, i get error message

EricG_1-1720552796711.png

The output message is as follows

{
"body":  "Cannot find an object with identity: \u0027ba65ed77-b8c1-4bbd-8469-34f7e5d2a3f1]\u0027 under: \u0027DC=XXXXXX,DC=Global\u0027.",
"status":  "Error"
}

My action is set as follows:

EricG_2-1720553002216.png

I've tried using a String for User Name and Group Name.

As well as using the AD Lookup GUID's and a combination of both.

 

Not sure why i can't add to the group (Permissions?) or what "Invalid Resource Name" means.

The support tech i opened a case with wasn't very helpful, as this seems to fall under the "Customization" rules.

 

Can anyone provide some guidance on this.  Or anything more i should provide to clarify.

7 REPLIES 7

Now Support replied to my case -- this is a known defect (PRB1788405). They were able to provide an update set as a workaround. I'm assuming I'm not supposed to post update sets provided by Support here, but if you open a case and reference that problem ID I'm sure they'll provide it to you as well.

Thanks Matt, we have raised a hi support case and we've been advised the same, cheers!