Hello, I have created a web-hook in Portal that subscribes to all groups events. When a user updates a group name in portal this web-hook is triggered and sends the payload to my API. My API validates the name and then updates the group name via the Portal REST API's if it is not in the correct format. This will then trigger the web-hook again as expected but won't update the group name now that it is valid. However a 3rd web-hook event is triggered and fails with the error message 'peer not authenticated'. This third event is only triggered after the update of the group name via the Portal REST API where 2 events are triggered rather than the expected 1.
This does not occur in our non-SSO environment and the 3rd webhook trigger never appears in the 'notificationStatus' history. I find the error confusing as the web-hook is able to communicate with my custom API to send the payload and my custom API is able to send successful requests via the Portal REST API's back.
Has anyone else experienced this and/or has a proposed solution?
EDIT: This issue is not related to SSO, we have narrowed down the problem. If a web hook is triggered and another trigger occurs before a response has been received for the 1st trigger then the 1st notification will time out regardless if a response has been received in time. The response from the 1st trigger is displayed on the notification status page proving that it did receive it.
This looks like a bug to me, would be grateful if someone could confirm. It seems like a common use case where a web-hook is triggered whilst another one is still awaiting a response.