IBM Support

IJ32157: UNABLE TO MAKE SOAP CALLS TO MEAWEB/SERVICES USING APIKEY WHEN USEAPPSERVERSECURITY IS TURNED ON.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • DESCRIPTION: As Idp Authentication is enabled, native
    authentication using MAXAUTH header cannot be used for the
    Webservice calls. For this use case, the apikey feature was
    designed to help headless interaction with OIDC or other
    similar federated (interactive) authentication schemes. The
    webservices calls still fail after using the APIKEY in the
    header.
     
    
    STEPS TO REPRODUCE:
    1) Create an apikey from the
    Administration work center.
    2) Make sure that the
    meaweb/services url is not secured using the app server
    security constraints block for web.xml
    3) Set the apikey as
    part of the SOAP(http request) header - header name is "apikey"
    - and make the request.
     
     
    RESULT:
    (1) The Webservice calls
    fails with the error similar to below at the SOAPUI.
    <faultcode>
    soapenv:Server</faultcode>
    <faultstring>javax.xml.ws.WebServiceE
    xception<faultstring>
     
    (2) Maximo logs point to below
    errors:
    [26.3.2021 12:23:31:425 EET] 00000131 LocalExceptio E
    CNTR0020E: EJB threw an unexpected
    (non-declared) exception
    during invocation of method "wsSecureProcessMOS" on
    bean
    "BeanId(MAXIMO#mboejb.jar#mosservice, null)". Exception
    data:
    java.lang.NullPointerException
     at psdi.security.SecurityS
    ervice.authenticateUserM(SecurityService.java:2108)
    .....
    psdi.i
    face.mos.MOSServiceBean.secureProcessMOS(MOSServiceBean.java:120
    )
    at psdi.iface.mos.MOSServiceBean.wsSecureProcessMOS(MOSService
    Bean.java:141)
    at psdi.iface.mos.EJSLocalStatelessmosservice_
    43
    551b5c.wsSecureProcessMOS(Unknown Source)
    at psdi.iface.webservi
    ces.OSWebServiceProxy.invokeService(OSWebServiceProxy.java:77)
    a
    t psdi.iface.webservices.JAXWSWebServiceProvider.invoke(JAXWSWeb
    ServiceProvider.java:149)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at s
    un.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorI
    mpl.java:90)
    at .....
    at org.apache.axis2.engine.AxisEngine.rece
    ive(AxisEngine.java:212)
    at org.apache.axis2.transport.http.HTTP
    TransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:17
    2)
    at com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(W
    ASAxis2Servlet.java:1633)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
    ...
    ......
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:
    1909)
    [26.3.2021 12:23:31:427 EET] 00000131 LocalTranCoor E
    WLTC0017E: Resources rolled back
    due to setRollbackOnly() being
    called.
    [26.3.2021 12:23:31:428 EET] 00000131 AxisEngine E
    org.apache.axis2.engine.AxisEngine
    receive An error was
    detected during JAXWS processing
    org.apache.axis2.AxisFault: An
    error was detected during JAXWS processing
    at
    org.apache.axis2.j
    axws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.ja
    va:20
     
     
    EXPECTED RESULT: The SOAP Webservice call should give
    the expected output and results without any error.
     
     
    REPORTED
    IN VERSION:
    Tivoli's process automation engine 7.6.1.2
    Tpae
    Integration Framework 7.6.1.2
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * UNABLE TO MAKE SOAP CALLS TO MEAWEB/SERVICES USING APIKEY    *
    * WHEN USEAPPSERVERSECURITY IS TURNED ON.                      *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:The fix for this APAR is contained in the following
    maintenance package: | release\fix pack\interim fix for Release
    7.6.1.3 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ32157

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-16

  • Closed date

    2021-05-05

  • Last modified date

    2021-05-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
06 May 2021