IBM Support

PM84207: GET API UNIQUENAME VALUE SHOULD BE IN NORMAL CASE AT THE TIME OF LOGIN.

Fixes are available

7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When externalIdAttributes is mapped to DistinguishedName.. for
    ExtId it returns DN of the entity in UPPER case which is
    expected.
    
    Before this fix when UniqueName is also passed in GET API call
    with normal case, GET API returns uniqueName in UPPER case
    also.
    
    
    After this fix when UniqueName is also passed in GET API call
    with normal case.. now it returns uniqueName in normal case
    simialr to the value that exists in LDAP repository.
    

Local fix

  • A temp fix is installed on the pre-production server for this
    customer. We need an offical iFix suitable for production
    server.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When externalIdAttributes is mapped     *
    *                      to DN, uniqueName is passed in GET      *
    *                      API with normal case, but GET API       *
    *                      returns in UPPER case.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When externalIdAttributes is mapped to DistinguishedName.. for
    ExtId it returns DN of the entity in UPPER case which is
    expected.
    when UniqueName is also passed in GET API call with normal
    case, GET API returns uniqueName in UPPER case also.
    

Problem conclusion

  • To fix this, you need to set a new custom property
    "returnUniqueNameInNormalCaseIfExtIdMapToDN" with value
    "true". This will return uniqueName in normal case
    simialr to the value that exists in LDAP repository in GET API
    when externalIdAttributes is mapped to DistinguishedName and
    uniqueName is passed in GET API call.
    
    In order to set this property, use the following command:
    
    $AdminTask setIdMgrCustomProperty {-id <LDAP_repos_ID> -name
    returnUniqueNameInNormalCaseIfExtIdMapToDN -value true}
    
    Here "LDAP_repos_ID" is the repository id of the LDAP
    configured in VMM. Also save the configuration after running
    the previous command using:
    
    $AdminConfig save
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.29, 8.0.0.7 and 8.5.5.1.  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

    PM84207

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-06

  • Closed date

    2013-04-24

  • Last modified date

    2013-04-24

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021