Legacy Knowledge Base
Published Jun. 30, 2025

How to manually trigger LDAP imports before the import interval is reached

Written By

Madeleine Clay

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • I want to manually trigger LDAP imports by triggering the UserImportConfigurationModelListener scheduled job.
  • However, when I trigger this job, I see the following line in the LDAP DEBUG logs:
DEBUG [liferay/scheduled_user_ldap_import-2][UserImportConfigurationModelListener:165] Skipping LDAP user import because LDAP import interval has not been reached

Environment

  • DXP 7.4

Resolution

  • To work around the import interval limit, set the System Settings Import Interval to the desired auto-import time, and the Instance Settings Import Interval to 1.

Additional Information

  • The UserImportConfigurationModelListener scheduled jog runs a series of checks to see if it can be triggered, one of which is to check whether the import interval set in the Instance Settings has been reached.
  • The System Settings import interval controls how often the scheduled job attempts to run. So if we set this to 10 minutes, every instance in the bundle will attempt to import users every 10 minutes.
  • Three checks may prevent importation; 1) import being disabled, 2) the Instance import interval being under 1 minute, and 3) the Instance import interval not having been reached.
  • There are three possibilities when setting the Instance import interval and the System import interval.
    1. If the Instance import interval is the same as the System import interval, then the imports are fired off every x minutes and all checks pass.
    2. If the Instance import interval is set higher than the System import interval, an import is attempted whether the System interval has been reached, but only allowed as often as dictated by the Instance interval.
    3. If the Instance import interval is set lower than the System import interval, then an import is attempted as often as is set in the System settings, but it can be triggered manually in the instance as soon as the Instance import interval has passed.

 

  • A feature request was opened at LPS-189362 to request that LDAP imports can be manually triggered before the interval is reached without the use of this workaround.
Did this article resolve your issue ?

Legacy Knowledge Base