Workflow Active Directory Action, Get user, Get Ou and move user not working

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi Experts,

  • Not able to get user using AD action> get user command using DN and SAMA account name

  • Similarily not able to move user to other OU using AD action > move user command.

  • Getting below error:
    {“error”"{"detailcode:“500.0 unhandled plugin error”,“message”:{“locale”:“en-us”;“locale-orgin”:“default”;"text:“LDAP result code 32 \“No such object\”: 0000208D: NameErr: DSID-03100245, problem 2001 (NO_OBJECT), data 0, best match of: \n\tDC=atest,DC=com’\n\u0000”}},“warnings”:"null,“result”:nu

  • User and OU are already present in AD.

  • When I’m searching user using AD actions > search user command, I’m getting back the user.

  • similarly, I’m able to search OU using AD actions > search OUs command.

    Any help, appreciated.

2

Could you provide more details from where you are running? and what command you are running?

3

Hello @suresh4iam,

I’m running the Active directory commands inside the workflow.

Workflow Actions - SailPoint Identity Services.

Command like search ou and search user are working fine.

But when I’m using the move user, get user using distinguished name and SAMA account name, I’m getting this error.

4

It seems that the user DN or Group DN is wrong, please double check it.

image
image359×473 11.9 KB

1 Like
5

Thank you, could you check the Workflow execution log and see what value you are getting in your DN and sAMAccountName attributes?

The object not found error is due to various reasons like DN value is not correct, like the path of DN, or the account moved to different location when the Workflow executing. Also, compare the DN attribute value with actual account location whether it matches.

6

I’ve doubled checked it, I’m able to get the same user and OU using search user and search OU’s command by passing the distinguished name as parameter.

So DN of user and DN of OU both are correct.

7

Okay, I understand you already checked but I’m still lieu on the DN variable which specifically passed to the failed case. If possible, could you share the Workflow execution log to have a look into it and the actual DN value with shadowed value.

1 Like
8

if not already doing, could you make sure to trim leading and trailing spaces or spl chars and pass it to the command.

9

Hello @lampard08,

There are no extra spaces, I’m directly passing DN of the user in “Get user using distinguished name” command.

10

Is it failing only for few identities or all? If it is all, I think you need to open a support case to have a look into it. Otherwise, compare failed identities with passed cases and see the differences.

1 Like
11

It is failing for all the identities.

Sure, I’ll raise the support ticket.

Thanks.

12

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