IBM Support

PI80689: Database persistence for tokens might not function correctly when the backing database does not support CLOB data types

Fixes are available

17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
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

  • When performing an OIDC flow with consent, using the
    "Consent
    and remember" button on the template will raise a FFDC and
    exception, the consent decision is not persisted, and on
    subsequent flows the user will be prompted for consent
    again.
    
    000000b2 id=
    com.ibm.ws.security.oauth20.plugins.db.DBConsentCache
    3
    Cannot get consent entry from DB ,
    
    
    org.postgresql.util.PSQLException: Bad value for type long :
    {"":""}
    com.ibm.ws.security.oauth20.plugins.db.DBConsentCache
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of Liberty Oauth and              *
    *                  OpenidConnect server features with database *
    *                  persistence                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Database persistence for tokens might   *
    *                      not function correctly when the backing *
    *                      database does not support CLOB data     *
    *                      types.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Code attempts to store a CLOB object without checking if the
    backing database supports CLOB.
    
    An FFDC entry similar to this might be seen:
    Stack Dump = org.postgresql.util.PSQLException: Bad value for
    type long : {"":""}
    at
    org.postgresql.jdbc2.AbstractJdbc2ResultSet.toLong(AbstractJdbc2
    ResultSet.java:2971)
    at
    org.postgresql.jdbc2.AbstractJdbc2ResultSet.getLong(AbstractJdbc
    2ResultSet.java:2163)
    at
    org.postgresql.jdbc2.AbstractJdbc2ResultSet.getClob(AbstractJdbc
    2ResultSet.java:436)
    at
    org.postgresql.jdbc2.AbstractJdbc2ResultSet.getClob(AbstractJdbc
    2ResultSet.java:424)
    at
    com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.getClob(WSJdbcResultSe
    t.java:754)
    at
    com.ibm.ws.security.oauth20.plugins.db.DBConsentCache.checkValid
    ityAndScopeAndResource(DBConsentCache.java:608)
    at
    com.ibm.ws.security.oauth20.plugins.db.DBConsentCache.get(DBCons
    entCache.java:558)
    

Problem conclusion

  • Code is updated to fall back to appropriate dataypes for
    databases that do not support CLOB.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.2  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

    PI80689

  • 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-04-27

  • Closed date

    2017-05-18

  • Last modified date

    2017-05-18

  • 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:
19 October 2021