Approved Tasks are Not Completed Due to "Error While Invoking ..workflowservice/CallbackService" with "WSM-07604 : Internal error during policy enforcement." and "WSM-07501" ERROR "Caused by: oracle.wsm.security.SecurityException: no protocol: localhost"
(Doc ID 2272957.1)
Last updated on JANUARY 14, 2020
Applies to:Identity Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Completed Approval Tasks are not shown as completed in OIM.
The SOA logs show an error invoking OIMs Callback service like Error while invoking endpoint "http(s)://oimExternalFrontendURL/workflowservice/CallbackService" from client
The SOA managed server diagnostic logs show several Warnings and Errors, including Warning WSM-07604 : Internal error during policy enforcement, and an WSM-07501 ERROR with "Caused by: oracle.wsm.security.SecurityException: no protocol: localhost" and "Caused by: java.net.MalformedURLException: no protocol: localhost" (even through the value of the <oimExternalFrontendURL> in the log was not "localhost"):
There was an 22.214.171.124.0 BI Publisher installation and an 126.96.36.199.0 OIM installation which used to have a shared Middleware home. At some point, the 188.8.131.52.x OIM installation was moved to a different machine by expanding the OIM domains cluster to include the new node, migrating the AdminServer to the new node - then updating the ORACLE_HOMES and other configuration files to point to the install bits on the new machine (paraphrasing here, not endorsing this method).
Then a new domain was created for the 184.108.40.206.0 BI Publisher installation but was pointed to the existing DB repositories from the old domain. After this, the OIM installation (on the new machine and in a separate domain) was upgraded from 220.127.116.11.x to 18.104.22.168.9 and the related MDS repository (which was still in use by the 22.214.171.124.6.0 BI Publisher domain) was also upgraded from 126.96.36.199.0 to 188.8.131.52.0 as part of the upgrade process. Then later, BI Publisher 184.108.40.206.0 was also installed on a third machine and another new domain was created for this installation which ALSO pointed to the 220.127.116.11.0 MDS repository on the existing DB.
These activities in and of themselves did not seem to result in the issue, as OIMs Request Approval functionality worked for several months later. However, at some point after this, it is possible that human error resulted in issuing the reset policy store command from the 18.104.22.168.0 BI Publishers' EM Console.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!