IBM Support

PM33256: SECJ0373E CANNOT CREATE CREDENTIAL FOR THE USER <NULL> FAILED VALIDATION OF LTPA STRINGINDEXOUTOFBOUNDSEXCEPTION. SECJ0305I

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
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If a client is using "Automatically generated server identity"
    with Federated Repository and performs Identity Assertion to a
    server using SAF User Registry, then the following problem may
    be seen in the server:
    
    Trace: 2011/02/17 01:54:08.619 01 t=AC4598 c=UNK key=S2
    (13007002)
       ThreadId: 0000002d
       FunctionName: com.ibm.ws.security.ltpa.LTPAServerObject
       SourceId: com.ibm.ws.security.ltpa.LTPAServerObject
       Category: SEVERE
       ExtendedMessage: BBOO0220E: SECJ0373E: Cannot create
    credential for the user <null> due to failed validation of the
    LTPA token. The exception is
    java.lang.StringIndexOutOfBoundsException
            at java.lang.String.substring(String.java:1092)
            at
    com.ibm.ws.security.ltpa.CrossRealmUtil.getCredForForeignUser(Cr
    ossRealmUtil.java:194)
    
    
    Following the above error a SECJ0305I error may surface as well:
    Trace: 2011/02/17 01:54:09.296 01 t=AC9360 c=UNK key=S2
    (13007002)
      ThreadId: 00000015
      FunctionName: com.ibm.ws.security.role.RoleBasedAuthorizerImpl
      SourceId: com.ibm.ws.security.role.RoleBasedAuthorizerImpl
      Category: AUDIT
      ExtendedMessage: BBOO0222I: SECJ0305I: The role-based
    authorization check failed for admin-authz operation
    RoutingLibraryDetection
    :getCurrentBundleStatesAsIntegers:java.util.List.  The user
    WDGUEST (unique ID: WDGUEST) was not granted any of the
    following requir
    ed roles: deployer, operator, configurator, monitor,
    administrator, adminsecuritymanager, auditor.
    
    For an ND system the SECJ0373E was seen in the Node Agent of the
    server's cell, and SECJ0305I was seen in the Application Server.
    For a Base server both errors may appear in the same server
    address spaces.
    

Local fix

  • In the Client's Admin Console:
    Security >  Secure administration, applications, and
    infrastructure >   Federated repositories > Configure.
    
    In the "Server user identity" section, change:
    "Automatically generated server identity"
    to:
    "Server identity that is stored in the repository".
    
    Use an ID that is present in both the Client and Server and has
    authorization to appropriate EJBROLE profiles in the Server.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application Server
    *                  V7.0                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: SECJ0373E error during remote RMI       *
    *                      call with security attribute            *
    *                      propgation enabled.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a generated server ID is used for server id on the client
    side, and it is being used as an asserted ID of identity
    assertion, the server side fails to construct the Subject
    because of missing realm name. The reason why the realm name
    is missing is that a user registry fails to validate
    automatically generated server id of which entry does not exist
    in the user registry.
    

Problem conclusion

  • With this fix, using a server Subject of the server side if a
    client sends a server ID as an identity assertion token.
    
    APAR PM33256 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.19 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM33256

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-21

  • Closed date

    2011-03-30

  • Last modified date

    2011-10-04

  • 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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK71280

       UP11/09/10 P F109

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM33256

Modified date: 04 October 2011