Access-request-status API needs some filtering work

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

The access-request-status API is falling short for meeting needs as follows.

When a significant outage occurred, sources failed in such a way that there are many requests in flight which will never finish. Unfortunately, that means managers are seeing lost requests.

I’ve been tasked with identifying these requests and cancelling them via the API.

There are a few ways I might retrieve a list of requests and begin finding the offending ones.

  1. Filter for requests since the date of the outage
  2. Find requests which include a specific source
  3. Find requests in a certain status
  4. Load every single request that has ever been made in our system and filter manually from this list of tens of thousands of requests.

The API documentation also shows there are some query fields available along with filter fields (which seems to only allow one property to be filtered). Why does this API use separate queries and filters? There are sorters also, which aren’t part of the filters.

2

Hi @rmccoy-unum,

The Access request module (and the API part) in IDN is kind of under-developed.

There is already an idea submitted for the API part asking for further enhancements.

For your use case, you may have to go the hard way of sorting every requests with the created/modified field and then pulling their accountActivityItemId to be used in the cancel request API.

3

Discussion at Navigate says there’s something new coming to this space in early 2025. Let’s hope it delivers the goods!