F5 APM logout URI compatibility with Java AJAX calls APP

We have an application hosted behind F5 named Tibco Spotfire where we succesfully do SSO, now we want to achieve logout by using the F5 logout URI which can be defined on the access policy. What we want is to achieve the following which is normal logout behavior. Keep in mind that we do SAML auth to internal SP, the application itself does not speak SAML.

The problem is that the first logout request is responded by the F5 APM with 200 OK, but the logout request is not being made to logout the F5 SAML SP session. This most certainly is prevented by the application itself because it is using Java AJAX scripting. Even redirecting the F5 to the /vdesk/hangup.php3 logout page is not working nor loaded because it is prevented on the clientside due to the same issue. I believe F5 uses the same Java coding to inititate the logout sequence, but due to incompatibility with the APP the F5 logout is not executed.

Ps: Had a similar issue with Sharepoint server logout which was solved by changing the Java response payload to include the /vdesk/hangup.php3 page to load after logout, this way both sessions were terminated successfully at the same time. So I want to achieve something similar.

Someone here in the F5 world already had similar compatibility issyes with Java AJAX based applications hosted behind F5 and using F5 APM logout URI feature? And how to solve this, perhaps there is a way to prioritize the F5 logout sequence on the client by adding some Java coding in response to client?

Thanks,

Marvin