IBM Support

PH14786: Using non ASCII characters (ex. Chinese) in an SCIM filter fails

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An SCIM filter containing non ASCII characters (for example:
    Chinese) fails with an HTTP 400 error code and an error
    message that includes CWIML5003W message that lists the a
    "com.ibm.ws.security.wim.scim.parser.TokenMgrError" as a
    reason for the failure.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  SCIM users with filters containing non      *
    *                  ASCII characters                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Using non ASCII characters (ex.         *
    *                      Chinese) in an SCIM filter fails        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An SCIM filter containing non ASCII characters (for example:
    Chinese) fails with an HTTP 400 error code and an error message
    that includes a CWIML5003W message that lists
    "com.ibm.ws.security.wim.scim.parser.TokenMgrError" as a reason
    for the failure.
    
    For example (where unicode_example is the unicode of the
    characters passed into the filter),
    {"Errors":[{"code":"400","description":"CWIML5003W: The
    'givenName co \"unicode_example\" or familyName co
    \"unicode_example\"' search filter cannot be parsed by the SCIM
    API for the following reason:
    com.ibm.ws.security.wim.scim.parser.TokenMgrError: Lexical error
    at line 1, column 15. Encountered: \"\unicode_example" (13850),
    after : \"\\\"\"","scimType":"invalidFilter"}]}
    

Problem conclusion

  • The code that parses the SCIM filter was updated to handle
    unicode or non ASCII characters.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 19.0.0.8.  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

    PH14786

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-22

  • Closed date

    2019-07-30

  • Last modified date

    2019-07-30

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • RCD0 PSY

       UP

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

Document Information

Modified date:
15 October 2021