Hi all, 
Short bug description:
The forwarderName attribute in GET /v2024/access-request-approvals/pending is displaying the wrong name.
Long bug description:
Have a role with manager as approval step for access request. Have 5 different identities (A,B,C,D,E) to be really clear on which values are being taken. Identity C must be the manager of identity B.
Log in as identity A and this role on behalf of identity B, whose manager is identity C.
Using the personal access token of identity D, fetch the data of GET /v2024/access-request-approvals/pending to get the id of the related pending approval, then call the API POST /v2024/access-request-approvals/:id/forward with the personal access token of identity D and forward the request to identity E, with comment TEST: reassigned from identity D.
Now look at GET /v2024/access-request-approvals/pending again and you will see the approval with the following attribute in forwardHistory:
"forwardHistory": [
{
"oldApproverName": "identity C",
"newApproverName": "identity E",
"comment": "TEST: reassigned from identity D",
"modified": "2024-11-07T12:53:29.048Z",
"forwarderName": "identity A",
"reassignmentType": "MANUAL_REASSIGNMENT"
}
]
The forwarderName attribute points to the original requester (identity A), but it should point to the identity who actually forwarded it (identity D), as can be seen by the documentation (and common sense): list-pending-approvals | SailPoint Developer Community
Tagging @jennifer_mitchell for awareness. I will submit a support ticket.
This looks like a similar issue as the bug below, but it occurs at a different location.
I’ve got to say I am surprised to see this bug exists, but also that it either hasn’t been detected before or fixed already.
Kind regards,
Angelo