Using the Approval Anywhere functionality with Starling Two Factor Authentication (2FA) app for mobile approvals of Safeguard password and session requests.
Users observe that the "approver" receives the request notification through Starling mobile app, and they are able to approve the request. However the approval does not reflect in the Safeguard interface for the requestor, and shows "approval pending".
It can happen with an Access Request Policy that has two or more approver users, (at least one of which is configured for Approval Anywhere), but only requires one approval. A push notification can get stuck.
When a request is made, the OneTouch push notification is received by the Approval Anywhere user(s) and the request gets approved first by a user logged into Safeguard, and then also via OneTouch. The Approval Anywhere request is now stuck - Safeguard polls Starling for the status of the request (approved), but when it tries to update the Access Request it fails because it has already been approved. This can snowball as more requests follow the same pattern, but at least Safeguard is still able process other Approval Anywhere requests.
Upgrading to 2.10 fixes all the above issues.