IBM Support

PI26950: MESSAGE "IRR012I VERIFICATION FAILED. USER PROFILE NOT FOUND"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Message "IRR012I Verification Failed. User profile not found"
    is seen when using the zosLocalAdapters (WOLA) service with a
    non-SAF user registry.
    The WebSphere Application Server for z/OS Liberty Profile
    server instance is attempting to authenticate users against
    SAF, regardless of which user registry is being used.  This
    happens when the zosLocalAdapters-1.0 service is enabled, and
    the angel process is started.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile for z/OS             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Some configurations unnecesarrily have  *
    *                      an implicit dependancy on having a      *
    *                      configured SAF registry.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An error like "IRR012I VERIFICATION FAILED. USER PROFILE NOT
    FOUND" may be issued when certain features (such as
    zosLocalAdapters) that rely on authorized services involving the
    Angel process are enabled, even though a SAF registry has not
    been configured and feature zosSecurity has not been enabled.
    

Problem conclusion

  • A code change has been made to avoid checking the SAF registry
    when it has not been configured.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.5.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • A workaround is to configure a SAF registry, for example:
    
    (a) Create SAF SERVER profile BBG.SECPFX.BBGZDFLT
    (b) Grant the Liberty Profile server READ to that profile
    (c) In the server.xml specify an ID that exists in SAF, or
    create
    'Fred' in SAF
    

Comments

APAR Information

  • APAR number

    PI26950

  • Reported component name

    LIBERTY - Z/OS

  • Reported component ID

    5655W6514

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-02

  • Closed date

    2015-02-03

  • Last modified date

    2015-02-03

  • 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

    LIBERTY - Z/OS

  • Fixed component ID

    5655W6514

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022