IBM Support

PM37108: WHEN HASHTABLE LOGIN IS USED, A SERVER FAILS TO START DUE TO SECJ0270E ERROR AFTER PM14768

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
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.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
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

  • Deployment manager could not start after WebSphere Application
    Server upgrade from 7.0.0.11 to 7.0.0.15, administrative
    security enabled.
    
    Following error logged in SystemOut.log from deployment manager.
    
    [4/8/11 17:04:33:292 CEST] 00000000 ContextManage E   SECJ0270E:
    Failed to get actual credentials. The exception is
    com.ibm.websphere.security.auth.WSLoginFailedException: This
    realm is not the current realm, nor the admin realm, nor a
    trusted realm: ldap
            at
    com.ibm.ws.security.server.lm.wsMapDefaultInboundLoginModule.
    validateInboundRealmIsTrusted(wsMapDefaultInboundLoginModule.jav
    a:2555)
            at
    com.ibm.ws.security.server.lm.wsMapDefaultInboundLoginModule.
    login(wsMapDefaultInboundLoginModule.java:882)
    

Local fix

  • Workaround - Disabled the Administrative security and deployment
    manager will start.
    
    We have disable security in the security.xml, then dmgr started
    successfully. We have added "ldap" to the trusted inbound realm
    under the federated repository configuration, enabled the server
    security and restarted the dmgr. Now it works fine with the
    added ldap truested realm. Before adding "ldap" as a trusted
    realm, only ldapserver:389 was on the trusted ldap realm list.
    
    security.xml
    
    ------------
      <inboundTrustedAuthenticationRealm
    xmi:id="TrustedAuthenticationRealm_1302278706158"
    realmList="ldap"/>
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server fails to   *
    *                      start if realm name contains "server:"  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A code, which extracts realm name from a given accessID,
    returns incorrect realm name if accessID string contains some
    specific patterens. For instance, if either realm name
    contains a string "server:", a realm name which this method
    returns is not correct.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM37108

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-04-15

  • Closed date

    2011-06-08

  • Last modified date

    2011-06-08

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVS22","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 June 2011