IBM Support

PI78326: WEBSPHERE SUB-DOMAIN SERVERS WITH SPNEGO WEB AUTHENTICATION GETTING ERROR SECJ6236E

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A server with SPNEGO TAI in domain XYZ is reconfigured to use
    SPNEGO Web Authentication and use a subdomain of ABC/XYZ.
    During server startup, several SECJ6236E messages appear in the
    servant region job log:
    SECJ6236E: Authorization failed; the exception is The SAF user
               SERVER1 does not have CONTROL access to the SAF
               profile CB.BIND.null,class CBIND..
    Also, the following message appear multiple times in the
    servant region SYSPRINT:
    Trace:2016/06/11 11:01:33.633 02 t=7B8E00 c=0.14 key=P8
            tag=(0401B03A)
      Description: ORB Trace Entry
      Method Name: ClassNameFromTypeId(char *)
      input type id: IDL:omg.org/CORBA/NO_PERMISSION:1.0
    Trace: 2016/06/11 11:01:33.633 02 t=7B8E00 c=0.14 key=P8
             tag=(0401B03F)
      Description: ORB Trace Exit
      Method Name: ClassNameFromTypeId(char *)
      output class name: CORBA::NO_PERMISSION
    Trace: 2016/06/11 11:01:33.633 02 t=7B8E00 c=0.14 key=P8
             tag=(0407900A)
      Description: demarshalJavaSystemException
      Method Name:
      ZIOPChannelBridge::demarshalJavaSystemException(EncapIIOP *)
      Repository Id: IDL:omg.org/CORBA/NO_PERMISSION:1.0
      Class Name: CORBA::NO_PERMISSION
      Minor Code: 4942430d
      Completion Status: 1
    It appears as though the servant never completely starts.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0, V8.5, abd V9.0                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Spnego authentication with SAF user     *
    *                      registry fails with the security        *
    *                      domain                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the application server is running under the security
    domain environment, Spnego authentication might fail due to a
    failure of invoking SAF user registry. The cause of the issue
    is that the security code does not set the server short name
    which is required for invoking SAF user registry.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI78326

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-16

  • Closed date

    2017-05-18

  • Last modified date

    2017-05-18

  • 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

  • R800 PSY

       UP

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

Document Information

Modified date:
18 May 2017