Description:
Symptoms
========
* Content for a user in a particular Role is not getting displayed
* Some portal administrators no longer have the ability to modify the portal
* Some of the Bins (such as Portal Pages) no longer appear in /portal_admin
* Random unexplained failures to deliver access controlled content to users


Impact
======
* Loss of Functionality
The portal will no longer function as expected, and random errors will start increasing.


Workaround
==========
There is no work-around for this issue.  The SUN LDAP must be upgraded to a version that does not have the problem.  


Cause
=====
There is a defect in the iPlanet and SUN LDAPs (before version 5.1, SP3) that causes this problem.  A complete description of the problem, how to determine if it exists, and a method for correcting it can be found in LBN article number 1-1IHM7L.

Incorrect data is being returned to PortalBuilder from the SUN LDAP. All operations pertaining to GROUPS could potentially fail, because the ID of the portal user or administrator cannot be correctly located.  For instance, LDAP operations such as add, delete, modify, or search do not return accurate results, and PB uses this data in the processing of the internal access control lists.


Resolution
==========
* The SUN LDAP must first be upgraded to a version that does not have the problem.  The vendor has outlined some specific steps in their README that must be followed, one of which is a complete export and import of all of the data contained in the LDAP.
* If your version of PortalBuider is earlier than 4.5.1 + HotFix1, you will also need to upgrade your version of PB.  For users of 4.5.1, please download and apply the latest HotFix (as outlined in the previous LBN article about this problem).  If you are using PB 4.5.2, no PB update is required.
Symptoms:

Cause:

Corruption of portal objects stored in the SUN Microsytems / iPlanet LDAP can cause unpredictable results in the portal.