PM47968: VMM OVERRIDES SEARCHBASES PASSED BY CLIENT WITH WIMCONFIG SEARCHBASE

8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Virtual member manager (VMM) ignores searchbases sent in
  client, it uses the configured searchbases for the entityType.
  
  
  <wim:controls xsi:type="wim:SearchControl" countLimit="4501"
  expression="@xsi:type='PersonAccount' and (uid = '*admin*')"
  timeLimit="600000">
  <wim:properties>uid</wim:properties>
  <wim:properties>mail</wim:properties>
  <wim:properties>AccountInactive</wim:properties>
  <wim:properties>title</wim:properties>
  <wim:properties>givenName</wim:properties>
  <wim:properties>CountryConfirmed</wim:properties>
  <wim:properties>sn</wim:properties>
  
  <wim:searchBases>ou=internal,ou=company,o=com</wim:searchBases>
  
  <wim:searchBases>ou=external,ou=company,o=com</wim:searchBases>
  </wim:controls>
  <wim:controls xsi:type="wim:SortControl">
  <wim:sortKeys>
  <wim:propertyName>sn</wim:propertyName>
  <wim:ascendingOrder>true</wim:ascendingOrder>
  </wim:sortKeys>
  <wim:locale>en_DE_DE</wim:locale>
  </wim:controls>
  </wim:Root>
  </sdo:datagraph>
  
  05.09.11 17:10:53:811 CEST] 00000045 WIMXPathInter 2
  com.ibm.ws.wim.xpath.WIMXPathInterpreter name name = uid
  [05.09.11 17:10:53:811 CEST] 00000045 WIMXPathInter 2
  com.ibm.ws.wim.xpath.WIMXPathInterpreter setPredicate Predicate
  condition : (uid = *admin*)
  [05.09.11 17:10:53:811 CEST] 00000045 LdapAdapter   >
  com.ibm.ws.wim.adapter.ldap.LdapAdapter getSearchFilter ENTRY
  [PersonAccount] [(uid = *admin*)]
  [05.09.11 17:10:53:811 CEST] 00000045 LdapXPathTran >
  com.ibm.ws.wim.xpath.ldap.util.LdapXPathTranslateHelper
  genSearchString(StringBuffer, ParenthesisNode) ENTRY [, (uid =
  *admin*)]
  [05.09.11 17:10:53:811 CEST] 00000045 LdapXPathTran >
  com.ibm.ws.wim.xpath.ldap.util.LdapXPathTranslateHelper
  genStringChild(StringBuffer, XPathNode) ENTRY [, uid = *admin*]
  [05.09.11 17:10:53:812 CEST] 00000045 LdapXPathTran <
  com.ibm.ws.wim.xpath.ldap.util.LdapXPathTranslateHelper
  genStringChild(StringBuffer, XPathNode) RETURN
  [05.09.11 17:10:53:812 CEST] 00000045 LdapXPathTran <
  com.ibm.ws.wim.xpath.ldap.util.LdapXPathTranslateHelper
  genSearchString(StringBuffer, ParenthesisNode) RETURN
  [05.09.11 17:10:53:812 CEST] 00000045 LdapAdapter   <
  com.ibm.ws.wim.adapter.ldap.LdapAdapter getSearchFilter RETURN
  [((uid=*admin*))]
  [05.09.11 17:10:53:812 CEST] 00000045 LdapAdapter   3
  com.ibm.ws.wim.adapter.ldap.LdapAdapter
  isEntitySearchBaseConfigured
  Search base is explicitly configured for PersonAccount:
  [ou=company,o=com]
  [05.09.11 17:10:53:812 CEST] 00000045 LdapAdapter   1
  com.ibm.ws.wim.adapter.ldap.LdapAdapter getLdapSearchControl
  Entity
  search base is configured, so realm search base will be ignored
  [05.09.11 17:10:53:812 CEST] 00000045 LdapAdapter   1
  com.ibm.ws.wim.adapter.ldap.LdapAdapter getLdapSearchControl
  Search base
  has been changed to entity search base
  
  
  In this way VMM overrides the searchbase passed by client. and
  uses the one configured in wimconfig.xml.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: VMM ignores searchBase sent over in the *
  *                      VMM search()/get() API call via         *
  *                      application.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Virtual member manager (VMM) does not honour searchBases sent
  in datagraph. And uses the one configured in wimconfig.xml.
  When a searchBase is sent in the dataGraph for search() or
  get() API call. It should be used for the same operation. But
  VMM picks up the one which's configured in wimconfig.xml file.
  

Problem conclusion

• The searchBases sent in dataGraphs will be used to refine
  search/get() operation.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.43 , 7.0.0.21 , 8.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 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 APP S

• Fixed component ID

  5724J0800

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

• R800 PSY

     UP