IBM Support

PI80547: Federated Repository's participatingBaseEntry element does not allow name attribute to be empty string

Fixes are available

17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A customer is able to specify an empty string for the
    'baseDN' attribute in the 'ldapRegistry' element but they
    are not able to specify an empty string for the 'name'
    attribute in the 'participatingBaseEntry' element for their
    'federatedRepository' configuration. This prevents the
    customer from being able to customize 'federatedRepository'
    configuration and use an LDAP registry that has a root
    baseDN.
    
        <ldapRegistry ... baseDN="" ... />
    
        <federatedRepository>
            <primaryRealm ...>
                <participatingBaseEntry name="" />
    
    The customer would currently get the following exception
    when trying to configure such a scenario:
    
    CWIMK0004E: The user registry operation could not be
    completed. The participating base entry definition  is not
    valid. Correct the participating base entry definition in
    the server.xml file. For example, the syntax is
    <participatingBaseEntry name="..."/>.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty- Virtual Member Manager      *
    *                  (VMM)                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Federated Repository's                  *
    *                      participatingBaseEntry element does not *
    *                      allow name attribute to be empty        *
    *                      string                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A customer is able to specify an empty string for the 'baseDN'
    attribute in the 'ldapRegistry' element but they are not able to
    specify an empty string for the 'name' attribute in the
    'participatingBaseEntry' element for their 'federatedRepository'
    configuration. This prevents the customer from being able to
    customize 'federatedRepository' configuration and use an LDAP
    registry that has a root baseDN.
    
        <ldapRegistry ... baseDN="" ... />
    
        <federatedRepository>
            <primaryRealm ...>
                <participatingBaseEntry name="" />
    
    The customer would currently get the following exception when
    trying to configure such a scenario:
    
    CWIMK0004E: The user registry operation could not be completed.
    The participating base entry definition  is not valid. Correct
    the participating base entry definition in the server.xml file.
    For example, the syntax is <participatingBaseEntry
    name="..."/>.
    

Problem conclusion

  • The participatingBaseEntry element's name attribute was updated
    to allow an empty string value.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.2.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI80547

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-25

  • Closed date

    2017-05-11

  • Last modified date

    2017-05-11

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021