Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-2370

User and UserGroup during LDAP Import at LP startup conflict with UserGroup templates having deployed portlet Plugins.

    Details

    • Branch Version/s:
      5.1.x

      Description

      • Start LP
      • Configure LP with an external LDAP; with import activated at startup.
      • First import : users, usergroups and memberships are imported.
      • Deploy some portlets plugins.
      • Create a set of pages on an imported userGroup.
      • Put portlets on theses page.
      • Synchronize with the ldap (without restarting LP)
      • Now, the users member of the group have personal comunity pages 'inherited' from the userGroup. Fine.
      • Stop LP
      • Start LP
      • During the startup, LP import the users/userGroup, rebuild the memberships ( ---> PortalLDAPUtil ---> UserLocalService(Util/Impl) ---> LayoutLocalService(Util/Impl) ---> LayoutImporter )
      • WARN : the PortletLocalServiceImpl raise a warning for each user of the group and for each portletPlugin, saying that the portlet is not there ! Sample here :
        _____________________________________________________________
        12:54:04,563 WARN [PortletLocalServiceImpl:155] Portlet not found for 10109 portlet_iframe_acces_porteurs_WAR_portlet_iframe_acces_porteurs_INSTANC
        E_0sL6
        12:54:04,660 WARN [PortletLocalServiceImpl:155] Portlet not found for 10109 portletSelector_WAR_portletSelector_INSTANCE_8qoN
        12:54:04,660 WARN [PortletLocalServiceImpl:155] Portlet not found for 10109 portlet_carte_WAR_portlet_widget_INSTANCE_9yKO
        12:54:04,661 WARN [PortletLocalServiceImpl:155] Portlet not found for 10109 portlet_meteo_WAR_portlet_widget_INSTANCE_GL9V
        12:54:04,661 WARN [PortletLocalServiceImpl:155] Portlet not found for 10109 portlet_calendrier_WAR_portlet_widget_INSTANCE_qdxy
        12:54:05,231 WARN [PortletLocalServiceImpl:155] Portlet not found for 10109 telegramme_zimbra_iframe_sso_WAR_telegramme_zimbra_iframe_sso_INSTANCE_
        5WEj
        _____________________________________________________________
        This occures even if the portlets WAR are already deployed or put in the deploy folder.

      It seems that the portlets are "mounted" after the ldap import.

      This is not blocking : after the LP startup is finished, everything is OK, the users have their personal pages, with the portlets on.

      But, if you have 1000 users in the usergroup, with 6 portlet plugins, the startup logs 6000 warning and spends about 20 minutes before allowing access to the portal...

      Is it possible to invert LDAP sync and Portlets mount order (but I don't know the impact...), perhaps via a portal property ?

        Attachments

          Activity

            People

            Assignee:
            support-lep@liferay.com SE Support
            Reporter:
            cariou Christophe Cariou
            Participants of an Issue:
            Recent user:
            Esther Sanz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since last comment:
              10 years, 44 weeks ago

                Packages

                Version Package