Automation of user creation in NERM

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

Hi,

I’m working on creating a contractor user in NERM through APIs using the profile endpoint. Currently, we have workflows set up in NERM and enter data manually into the forms, which creates both the personal and assignment profiles. I now want to automate this process in ISC by retrieving user data and making API calls to the NERM endpoints.

Before building the automation workflow in ISC, I want to test it in Postman. I used the following JSON body in the create profile request, assuming Id, uid, and person_id would be auto-generated. However, I received this error:

{
“error”: “param is missing or the value is empty: profile”
}

Here’s the JSON I tried:

{
“name”: “ABC”,
“profile_type_id”: “def48fcf-dcbd-48a5-bd2b-ac137cf48117”,
“status”: “Active”,
“id_proofing_status”: “pending”,
“attributes”: {
“assignment_rr_person”: “ABC”,
“email_address”: “ABC email”,
“first_name”: “A”,
“last_name”: “BC”,
“user_name_ne_attribute”: “ABC”
}
}

let me know the process for user creation , thanks in advance

2

Hi @sthumu ,

In looking at the NERM API Documentation for this endpoint, it does look like your body isn’t correct. Here is an example body which includes the ‘profile’ JSONObject:

{
  "profile": {
    "name": "First Last",
    "profile_type_id": "79ed1cb6-9977-4965-9bfe-f2bcc2424444",
    "status": "Active",
    "id_proofing_status": "pass",
    "archived": false,
    "attributes": {
      "text_attribute_uid": "static text",
      "date_attribute_uid": "01/15/2020",
      "profile_select_attribute_uid": "79ed1cb6-9977-4965-9bfe-f2bcc242523e",
      "multiple_profile_select_attribute_uid": "59ed1cb6-9977-4965-9bfe-f2bcc242523e, 89ed1cb6-9977-4965-9bfe-f2bcc242523e",
      "profile_search_attribute_uid": "79ed1cb6-9977-4965-9bfe-f2bcc242523e",
      "multiple_profile_search_attribute_uid": "59ed1cb6-9977-4965-9bfe-f2bcc242523e, 89ed1cb6-9977-4965-9bfe-f2bcc242523e",
      "contributor_select_attribute_uid": "49ed1cb6-9977-4965-9bfe-f2bcc2425244",
      "contributor_search_attribute_uid": "49ed1cb6-9977-4965-9bfe-f2bcc2425244",
      "multiple_contributor_search_attribute_uid": "59ed1cb6-9977-4965-9bfe-f2bcc242523e, 89ed1cb6-9977-4965-9bfe-f2bcc242523e",
      "owner_select_attribute_uid": "79ed1cb6-9977-4965-9bfe-f2bcc242523e",
      "owner_search_attribute_uid": "79ed1cb6-9977-4965-9bfe-f2bcc242523e",
      "dropdown_attribute_uid": "yes, no",
      "tags_attribute_uid": "yes, no",
      "checkbox_attribute_uid": "yes, no",
      "text_area_uid": "static text",
      "radio_attribute_uid": "yes, no"
    }
  }
}
3

@sthumu As Zach mentioned, the syntax in your post body appears to be incorrect, {
"profile": { is missing.

Additionally, make sure If you’re referencing an existing profile or user (including contributors), you need to pass the UUID.

To automate this process, you should first search for each attribute or profile in NERM. If it already exists, retrieve the corresponding UUID and then proceed with the post request , if you are using this method.

you can create workflow in ISC and NERM : sample from ISC

  • First step is schedule / frequency
  • get call , aggregate the profiles /users from source
  • call workflow which you will need to create in NERM, as described below.
  • create workflow in NERM , which checks for existing profile , if not create

image
image946×870 80.2 KB

Also, the scenario you described relates to profile synchronization or creation from ISC to NERM, not user synchronization. Please note that in NERM, users and profiles are distinct entities.



{
  "profile": {
    "name": "First Last",
    "profile_type_id": "79ed1cb6-9977-4965-9bfe-f2bcc2424444",
    "status": "Active",
    "id_proofing_status": "pass",
    "archived": false,
    "attributes": {
      "text_attribute_uid": "static text",
      "date_attribute_uid": "01/15/2020",
      "owner_select_attribute_uid": "<uuid>",
      "owner_search_attribute_uid": "<uuid>",
      "dropdown_attribute_uid": "yes, no",
      "tags_attribute_uid": "yes, no",
      "checkbox_attribute_uid": "yes, no",
      "text_area_uid": "static text",
      "radio_attribute_uid": "yes, no"
    }
  }
}
5

Hi @sanskriti_sanghvi @zachm117, thanks for highlighting the missing syntax. I’m now able to create profiles and assignment profiles for temporary identities, but some attributes like person_id, manager and assignment_id are still missing.

We have workflows in NERM designed to generate these values according to the defined logic.

@sanskriti_sanghvi, you shared the workflow snapshot showing calls to NERM workflows from ISC workflows. I see there’s an endpoint to get workflow IDs in NERM via the workflow action endpoint. How do we call these from ISC workflows?