IBM Support

PM20163: OBJECT GRID CLIENT FAILING WITH CORBA.NO_PERMISSION: ERROR; UNAUTHENTICATED CREDENTIAL FOUND.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Object grid Client failing with CORBA.NO_PERMISSION: ERROR;
    Unauthenticated credential found.
    Caused by: org.omg.CORBA.NO_PERMISSION: ERROR: Unauthenticated
    credential found, client auth required by client or server,
    throwing NO_PERMISSION. vmcid: 0x49421000 minor code: 92
    completed:
    com.ibm.websphere.objectgrid.TargetNotAvailableException
    com.ibm.ws.objectgrid.client.ORBClientCoreMessageHandler.get 160
    Exception =
    com.ibm.websphere.objectgrid.TargetNotAvailableException
    Source =
    com.ibm.ws.objectgrid.client.ORBClientCoreMessageHandler.get
    probeid = 160
    Stack Dump =
    com.ibm.websphere.objectgrid.TargetNotAvailableException: cannot
    find primary target after retries for
    ObjectGrid=P2KH1B2ELowVolGrid:RequestFrameworkMapSet and
    partition=17, check your server status
    

Local fix

  • Change the client authentication to "Supported" on the server
    side.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere eXtreme Scale        *
    ****************************************************************
    * PROBLEM DESCRIPTION: A "NO_PERMISSION" exception displays    *
    *                      with the following                      *
    *                      message: "Unauthenticated               *
    *                      credential found, client auth           *
    *                      required by client or server."          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere Application Server security context was not available
    on client thread. This client request is therefore rejected by
    server because authentication is set to 'Required' on server sid
    

Problem conclusion

  • To prevent the "NO_PERMISSION" exception, this fix adds
    security context on all client threads to correct this problem.
    
    A future cumulative fix corrects the problem for WebSphere
    eXtreme Scale Versions 6.1, 7.0 and 7.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM20163

  • Reported component name

    XD EXTREME SCAL

  • Reported component ID

    5724J3402

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-08-09

  • Closed date

    2010-09-13

  • Last modified date

    2010-09-13

  • 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

    XD EXTREME SCAL

  • Fixed component ID

    5724J3402

Applicable component levels

  • R610 PSY

       UP

  • R700 PSY

       UP

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 September 2020