IBM Support

PI17239: PRINCIPAL NAME FOR THE USERS IN LOCAL OS AND DOMAIN RETURNED IN THE FORMAT MACHINEID\USERID OR DOMAIN\USERID

Fixes are available

7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Whenever a user logged into WebSphere Application Server,
    virtual member manager (VMM) returned principal name of the
    user in the format "machineid\userid" if user defined in local
    OS or "domain\userid" if user defined in domain (configured as
    URBridge in Federated repository)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: For users defined in Local OS or        *
    *                      domain VMM returns principal name in    *
    *                      format machineid\userid or              *
    *                      domain\userid                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Whenever a user defined in the Local Operating System or
    domain configured as URBridge in Federated Reposiotry logged
    into WebSphere Application Server, VMM returned principal name
    of the user in the format "machineid\userid" or
    "domain\userid".
    

Problem conclusion

  • To fix this, a custom property
    "localAndDomainRegistryReturnPrincipalNameAsUserId" needs to
    be added while configuring Local OS registry(URBridge) in VMM,
    The value of the custom property is set to "userId". Once this
    property is set, the machineid or domain information will be
    removed from the principal name.
    
    In order to set this property, use the following command:
    
    $AdminTask setIdMgrCustomProperty { -id
    <LocalOS_Repository_Id> -name
    localAndDomainRegistryReturnPrincipalNameAsUserId -value userId}
    
    Here "LocalOS_Repository_Id" is the repository id of the Local
    OS 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.35, 8.0.0.10 and 8.5.5.4.  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

    PI17239

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-05-02

  • Closed date

    2014-07-25

  • Last modified date

    2015-01-15

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI17239

Modified date: 15 January 2015