PK93243: VMM SEARCH WITH PROPERTIES THAT ARE NOT DEFINED DIDN'T CAUSE SEARCH FAILURE.

Fixes are available

APAR status

Closed as program error.

Error description

When searching for Groups with givenName="w*" or
cn="w*" in certain configurations (for example with LA), the
search fails with stack trace indicating that givenName is not
defined.
However, in other configurations (for example Ldap), the
un-defined search property is ignored and search returns with
results for cn="w*".

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server v6.1 or v7.0 who use federated       *
*                  repositories (VMM - virtual member manager) *
****************************************************************
* PROBLEM DESCRIPTION: A search with an undefined property     *
*                      did not cause a search API failure.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The scenario below describes the failure:
An extension property 'employeeID' is added to VMM for entity
PersonAccount only, this attribute is stored in Ldap, no LA is
configured.
    <wim:propertySchema nsPrefix="wim"
nsURI="http://www.ibm.com/websphere/wim" dataType="STRING"
       multiValued="false" propertyName="employeeID">
<wim:applicableEntityTypeNames>PersonAccount</wim:applicableEnti
tyTypeNames>
    </wim:propertySchema>

search with property 'employeeID' for entity Group should fail
because this property was not defined for Group, but it didn't
cause a VMM search() API failure, and the undefined property
'employeeID' was just ignored and search results can be
returned.

"@xsi:type='Group' and (cn='wpsadmins*') or (employeeID =
'de*')"

Problem conclusion

This is not the correct scenario. It has been fixed, if there
is an undefined property specified in a search filter, VMM
search() API call will fail with an exception.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.29 and 7.0.0.9  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
PK93243
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-06
Closed date
2009-09-18
Last modified date
2009-10-02

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

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

Document Information

Modified date:
29 December 2021

Tips

PK93243: VMM SEARCH WITH PROPERTIES THAT ARE NOT DEFINED DIDN'T CAUSE SEARCH FAILURE.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?