IBM Support

PI84036: JAX-RS Client must access endpoints via authenticating proxy

Fixes are available

17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In some cases, users need to use the JAX-RS Client APIs to
    access remote URL endpoints that must pass through an
    authenticating proxy server.  An authenticating proxy server
    is similar to a proxy server, but requires that the client
    be given special authorization to access the remote
    endpoints.  WebSphere Liberty has no mechanism for users to
    specify Basic authorization credentials for authenticating
    with a proxy server.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - JAX-RS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: JAX-RS Client must access endpoints via *
    *                      authenticating proxy                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In some situations, users need to use the JAX-RS Client APIs to
    access remote URL endpoints that must pass through an
    authenticating proxy server.  An authenticating proxy server is
    similar to a proxy server, but requires that the client be given
    special authorization to access the remote endpoints.  WebSphere
    Liberty has no mechanism for users to specify Basic
    authorization credentials for authenticating with a proxy
    server.
    

Problem conclusion

  • The fix for this APAR adds new configuration properties for the
    JAX-RS Client that enables proxy authentication.  They are:
    com.ibm.ws.jaxrs.client.proxy.username
    com.ibm.ws.jaxrs.client.proxy.password
    
    These properties must be used with existing proxy configuration
    properties.  Here is an example of how these properties could be
    used in JAX-RS Client API code:
    
    ClientBuilder cb = ClientBuilder.newBuilder();
    cb.property("com.ibm.ws.jaxrs.client.proxy.host", host); //
    hostname or IP address of the proxy server
    cb.property("com.ibm.ws.jaxrs.client.proxy.port", port);  // TCP
    port for the proxy server
    cb.property("com.ibm.ws.jaxrs.client.proxy.username", username);
    // username of the user to
    cb.property("com.ibm.ws.jaxrs.client.proxy.password",
    password);
    Client c = cb.build();
    String response =
    c.target(targetURL).request().get(String.class); // targetURL is
    the remote endpoint that requires a proxy to access
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.3.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI84036

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-05

  • Closed date

    2017-08-10

  • Last modified date

    2017-08-10

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021