Highlighted
Respected Contributor.
Respected Contributor.
459 views

IDM 4.8.x: Soap getWorkEntries failed

Jump to solution

Hi all,

since IDM 4.8 i get problems with the SOAP Call getWorkEntries against "IDMProv/provisioning/service".  If i do the same request aginst IDM 4.7 -> success.

I check the entries more then one time and the idmdash shows me all work entries. The WSDL is the same as IDM 4.7, i think there is a problem in IDMProv.

Could anyone check that request with SOAP UI or something else and give me an feedback. If there more people with the same problem i would open an SR.

Many thanks for you help

regards

Taito

Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.novell.com/provisioning/service">
<soapenv:Header/>
<soapenv:Body>
<ser:getWorkEntriesRequest>
<ser:WorkEntryQuery logic="OR" order="CREATION">
<ser:recipient>cn=test1,o=data</ser:recipient>
<ser:recipient>o=data</ser:recipient>
<ser:initiator>cn=test1,o=data</ser:initiator>
</ser:WorkEntryQuery>
<ser:arg1>-1</ser:arg1>
</ser:getWorkEntriesRequest>
</soapenv:Body>
</soapenv:Envelope>

 

Response:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>Client</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<ns1:AdminException xmlns="http://www.novell.com/provisioning/service" xmlns:ns1="http://www.novell.com/provisioning/service">
<ns2:reason xmlns="http://www.novell.com/soa/af/impl/soap" xmlns:ns2="http://www.novell.com/soa/af/impl/soap">An error occurred, during retrieving work details.</ns2:reason>
</ns1:AdminException>
<stackTrace xsi:type="xsd:string">com.novell.soa.af.impl.soap.AdminException={_Reason=An error occurred, during retrieving work details.}
at com.novell.soa.af.impl.soap.ProvisioningImpl.createAdminException(ProvisioningImpl.java:428)
at com.novell.soa.af.impl.soap.ProvisioningImpl.getWorkEntries(ProvisioningImpl.java:2406)
at com.novell.soa.af.impl.soap.Provisioning_ServiceSkeleton._invoke(Provisioning_ServiceSkeleton.java:400)
at com.novell.soa.ws.server.ServletSkeleton.invokeEndPoint(ServletSkeleton.java:244)
at com.novell.soa.ws.impl.soap.MessageHandlerInvoker.invokeServerMessageHandlers(MessageHandlerInvoker.java:348)
at com.novell.soa.ws.impl.soap.SOAPHandler.handleServerRequest(SOAPHandler.java:84)
at com.novell.soa.ws.impl.rpc.ServerDelegateImpl.handleServerRequest(ServerDelegateImpl.java:92)
at com.novell.soa.ws.server.ServletSkeleton.handleRequest(ServletSkeleton.java:105)
at com.novell.soa.ws.server.ServletSkeleton.doPost(ServletSkeleton.java:366)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at com.novell.common.auth.JAASFilter.doFilter(JAASFilter.java:149)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at com.novell.common.auth.saml.AuthTokenGeneratorFilter.doFilter(AuthTokenGeneratorFilter.java:119)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at com.novell.common.auth.sso.SSOFilter.doFilter(SSOFilter.java:165)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at com.novell.soa.common.i18n.BestLocaleServletFilter.doFilter(BestLocaleServletFilter.java:241)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:126)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at com.novell.common.ForceNoCacheFilter.doFilter(ForceNoCacheFilter.java:69)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at com.novell.common.CrossScriptingFilter.doFilter(CrossScriptingFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at com.novell.common.HttpSecurityHeadersFilter.doFilter(HttpSecurityHeadersFilter.java:132)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:373)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)</stackTrace>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Labels (1)
1 Solution

Accepted Solutions
Highlighted
Respected Contributor.
Respected Contributor.

Hi all

same problem, i have open a SR and this is the response

Hi Hernan,

Regarding your Service Request with the following Brief Description:
"SOAP Services Work Entries problem"

This issue is a known  (internal) bug:
1172199 com.novell.soa.af.rest.controller returns NPE while trying to view workflow details in iManager”

The target milestone for fix has been set to Identity Manager 4.8.2
Identity Manager 4.8.2 is scheduled to be released in the September / October 2020 time frame.


Best regards,

View solution in original post

11 Replies
Highlighted
Respected Contributor.
Respected Contributor.

Hi all

same problem, i have open a SR and this is the response

Hi Hernan,

Regarding your Service Request with the following Brief Description:
"SOAP Services Work Entries problem"

This issue is a known  (internal) bug:
1172199 com.novell.soa.af.rest.controller returns NPE while trying to view workflow details in iManager”

The target milestone for fix has been set to Identity Manager 4.8.2
Identity Manager 4.8.2 is scheduled to be released in the September / October 2020 time frame.


Best regards,

View solution in original post

Highlighted
Respected Contributor.
Respected Contributor.
Thank you, you made my day 😉
regards
Taito
Highlighted
Knowledge Partner
Knowledge Partner

Ran into this at two client sites.  They were able to get a patched IDMProv.war from Support that is an early build of what will be in 4.8.2.

 

If you push support you should be able to get the patch to resolve it.

 

Highlighted
Respected Contributor.
Respected Contributor.
Hi all
If anyone can get the patch please just let me know. Anyway if I can get it, I will notice you
Many thanks to all
Highlighted
Respected Contributor.
Respected Contributor.
Thank you for the hint -> tomorrow i will get in touch with MF.

best regards
Taito
Highlighted
Respected Contributor.
Respected Contributor.

Hi Taito,

Finally i have the patch from support, the call getWorkEntries works fine but the call reassignWorkTask doesn’t works.

Do you have the patch?

Thank you

Highlighted
Knowledge Partner
Knowledge Partner

The same customer of mine that got the patch for getWorkEntries just identified this issue as well, the forward() has issues when there is a null value, which it seems likely to me is related.

Again, I would ask support.  If they have a fix, it would be they who can provide it.

My understanding is at least the getWorkEntries would be in the 4.8.2 patch due in the next few months. (I heard a date I chose not to repeat).

Highlighted
Respected Contributor.
Respected Contributor.
thanks geoffc for the further informations..

bad news 😞

Taito
Highlighted
Respected Contributor.
Respected Contributor.

Hi all,

i also get the patch from support, but the problem is not finally fixed - same results.

so i wait and leave my SR open.

best regards

Taito

Highlighted
Knowledge Partner
Knowledge Partner

I can report that in two locations where I applied that patch, it resolved the getworkentries problem.

There is a further issue that I am told is due in SP2, which is due out sometime soonish.  (I had heard a date I won't mention that has mostly passed already. But welcome to software development, testing/QA/etc are slow and sometimes find issues.).

0 Likes
Highlighted
Respected Contributor.
Respected Contributor.
Hi Hernanco,

at the moment i wait for an answer from my MF contact - that means at the moment i doesn't have the patch.

But after i read your message - its not final patched - sounds bad.

Taito
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.