Get archived profiles from NERM API?

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

Is there a way to pull archived profile data from the NERM API? If I have a profile id that’s been archived and use the /profiles endpoint I get a 400 “error”: “profile not found”. I can validate that the profile id by pasting it into the /neprofile_admin/profiles/ in the browser.

As a workaround I inspected how the web UI is returning archived results - I’m able to query the /react/admin/ endpoint using the session token from the browser, but that’s not really a sustainable solution.

2

I believe you should be able to do that with an advanced search:

3

Thanks Edwin. I might be configuring my advanced search wrong, but it’s only returning profiles in active/inactive status. Is there an example somewhere that I can work from? Here’s the body I’m posting:


{
  "advanced_search": {
    "label": "archived_contractors",
    "condition_rules_attributes": [
      {
        
        "type": "ProfileStatusRule",
        "comparison_operator": "==",
        "value": "Terminated"
      },
      {
        "type": "ProfileTypeRule",
        "comparison_operator": "==",
        "value": "$env:contractors"
      }
    ]
  }
}

When I add another condition with a value specific to an archived profile it returns no results, but when I replace that with a value specific to a non-archived (but still status=Terminated) profile it returns the expected profile. Any thoughts?

Also, assuming I do have something missing in my search syntax, how does pagination work with advanced search? Seems that it only returns a max of 100 results…

4

Answer for anyone who stumbles on this:
Submitted a ticket on this and was told that the ‘after_id’ query parameter will allow you to pull archived profiles.

Unfortunately, there’s no way to get a specific profile id with this method - the only filtering you can really do is profile_type. So for my example above I had to do something like this:

/api/profiles?profile_type_id=$env:contractors&after_id&&limit=500&metadata=true

We have 30k total active and archived profiles of this type, so I had to paginate with the _metadata.after_id value and loop until my result count was less than 500. The nice thing is that your limit per call is 500 instead of 100, but still took a few minutes for me to pull them all down :slight_smile:

5

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