IBM Support

PI60355: OAUTH2 PROVIDER EXPIRED TOKENS ARE NOT REMOVED WHEN DATABASE IS INCOMPATIBLE WITH ITS SQL QUERIES

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Using OAuth2 provider with WebSphere Application Server, when
    the getExpiredCount method of the
    com.ibm.ws.security.oauth20.plugins.db.CachedDBTokenStore class
    is called, it causes an SQLException to be thrown and the
    method returns -1 (and therefore expired tokens are never
    removed).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: OAuth TAI SQL query may cause           *
    *                      java.sql.SQLException                   *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack that contains this       *
    *                  APAR.                                       *
    ****************************************************************
    When the OAuth Trust Association Interceptor (TAI) uses a
    a Java Database Connectivity (JDBC) database store, it uses
    specific SQL queries to retrieve expired tokens.  Some of the
    SQL queries it uses may be incompatible with datbases such as
    Informix.
    

Problem conclusion

  • The OAuth TAI is updated so that it can use an alternate query
    to retrieve expired tokens.  A new OAuth provider
    configuration property is added:
    
    oauthjdbc.AlternateSelectCountQuery
    
    If, at runtime, you receive a java.sql.SQLException, set this
    custom property to true in your OAuth provider configuration
    file:
    
    <parameter name="oauthjdbc.AlternateSelectCountQuery" type="ws"
      customizable="false">
      <value>true</value>
    </parameter>
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.43, 8.0.0.12 and 8.5.5.10.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    Keywords: IBMWL3WSS, OAUTH
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI60355

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-06

  • Closed date

    2016-04-25

  • Last modified date

    2016-04-25

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI60355

Modified date: 25 April 2016