Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

AD Group creation via API is failing

FabianaS
New Contributor II
New Contributor II

Hi,

We are fully able to create AD group from UI via "Create AD Group" tile. After approval, a task is generated and the group is created on Active Directory after running provisioning job.

We are not succeeding at same operation done via API call from Postman: {{url}}/ECM/{{path}}/createrequest 

The API call is successfully performed since we are receiving 200 OK code.

In Saviynt the request to create a new group is received and we can approve it. 

The task is successfully created (in pending task) but when we execute the task (provisioning job), the following error is raised:

<br> Error while Create operation for Entitlment-CN=TestFromAPI_3,OU=Group,OU=xxx,DC=clientx,DC=clienty inAD, Exception : Error while GROUP CREATION IN AD

how can we solve it? thank you

4 REPLIES 4

Saathvik
All-Star
All-Star

@FabianaS :

Please mask any sensitive information.


Regards,
Saathvik
If this reply answered your question, please Accept As Solution and give Kudos to help others facing similar issue.

FabianaS
New Contributor II
New Contributor II

This was the original createUpdateMappings JSON:


{
"cn": "${role?.customproperty27}",
"objectCategory": "CN=Group,CN=Schema,CN=Configuration,${role?.customproperty23}",
"d
isplayName": "${role?.displayname}",
"SamAccountName": "${role?.displayname}",
"description": "${role?.description}",
"objectClass": "group",
"name": "${role?.customproperty27}"
}

We modified it as following: 

{
"cn": "${role?.description}",
"objectCategory": "CN=Group,CN=Schema,CN=Configuration,DC=clientXX,DC=zzz",
"displayName": "${role?.displayname}",
"SamAccountName": "${role?.displayname}",
"description": "${role?.description}",
"objectClass": "group",
"name": "${role?.customproperty27}"
}

And now creation of AD Groups from Postman with API is working.

Thank you for your help.

Now the next step is to make those creations Auto-Approved and we are not succeeding. We will open a new post in the forum for this problem. Thank you

  • You need to update workflow logic to get auto approved.
  • 👍Please click the 'Accept As Solution' button on the reply (or replies) that best answered your original question.

Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

rushikeshvartak
All-Star
All-Star

It seems you are not passing all attributes as configured on gsp and not getting passed to respective role customproperty.

please share postman screenshot masking sensitive information 


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.